https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243094
--- Comment #6 from Bernhard Berger <bernh...@blberger.de> --- (In reply to Conrad Meyer from comment #5) I am a user and use FreeBSD as a server system for a home server. What I really liked about FreeBSD was the ports system. Of course, between ports that are not part of the FreeBSD system, you have to evaluate differently than programs that are part of the system. A program that says what it does by name must also do exactly what it says by name. reboot >>>> System reboot shutdown -r now >>> System reboot reboot <<< do the same >>> shutdown -r now at least by all appearances. I found out by accident that reboot does not execute the script /etc/rc.shutdown(logs). And therefore not the service vm! VM's take a long time to shut down and are then simply shot down and I have always wondered about VM's being shot AFTER using reboot. Then I always manually stopped all VM#s before a reboot. Often the system got stuck and had to be rebooted by me via power off/on with anxious in my heart if everything will start well again. And as it looks it is reboot that caused all the trouble. I never expected such an error. But this is a big mistake, because basically "MUST" reboot does the same as shutdown -r now and this is because that's what the name "reboot" says. You should not ignore this problem. I am very disappointed ps: i am now thinking about switching to linux or windows. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
