Date: Tue, 23 Jul 2002 23:55:18 -0700 (PDT) From: "Roberto E. Medina" <theartofbone@hotmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/40946: Possible way to cause a system to hang using FreeBSD 4.6 remotely. Message-ID: <200207240655.g6O6tIEo078320@www.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 40946 >Category: i386 >Synopsis: Possible way to cause a system to hang using FreeBSD 4.6 remotely. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 24 00:00:11 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Roberto E. Medina >Release: 4.6 >Organization: West Texas Perfusion >Environment: Machine is crashed... can't do this. I have to go in person to hit the reboot button since remote administration is now impossible till it gets a cold boot. >Description: Well, I set up a FreeBSD 4.6 box to host my new domain and get sendmail to work and finally got it... sort of. see (http://www.linuxnewbie.org/forum/showthread.php?s=&threadid=56505) for more info... >How-To-Repeat: I logged in as sys admin user (wheel group), su -'d to root, did pico /etc/rc.conf, and changed my hostname (my fully qualified domain name..) setting over an ssh connection w/ putty release 0.52. This managed to crash the machine upon the su -'d user saving the file (/etc/rc.conf) and striking a key. All this on FreeBSD 4.6. >Fix: I don't know if its a TRUE problem, but it's happened once. The remote machine is like 30 miles away, so I still haven't gotten a chance to reboot it and retry. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207240655.g6O6tIEo078320>