Date: Tue, 9 Mar 1999 17:50:02 -0800 (PST) From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/10035: 3.0-STABLE, rc.shutdown is still ignored. Message-ID: <199903100150.RAA56892@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/10035; it has been noted by GNATS. From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: freebsd-gnats-submit@freebsd.org, philip@eilio.com Cc: Subject: Re: bin/10035: 3.0-STABLE, rc.shutdown is still ignored. Date: Tue, 09 Mar 1999 17:48:39 -0800 I've been asking myself this question myself, since upgrading from 2.2.8 to 3.1.0 and receiving many more . After looking at the source, shutdown -r, which performs a reboot(), will not run rc.shutdown. To run rc.shutdown, you need to do a shutdown now. I've been thinking that to perform a reboot you will need to create a shell script to [for example] touch a file in /var/run, then issue a shutdown now. rc.shutdown would reboot, halt, or go sigle-user based upon which file would exist (or the contents of the file) in /var/run. In a sense this is vaguely similar in function what the SYSV init does when you send it an "init 6" or "init 0". Reboot(2) on the other hand is a system call that syncs the file systems and reboots or shuts down. I suppose that reboot could signal init to run rc.shutdown, however this would be more consistent with SYSV rather than BSD. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC 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?199903100150.RAA56892>