Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 05 Jan 2020 19:37:54 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 243094] reboot problem
Message-ID:  <bug-243094-227-v9b7JNMK5H@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-243094-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-243094-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243094

--- Comment #6 from Bernhard Berger <bernhard@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.=20
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 differe=
ntly
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=20

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 aga=
in.=20
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.=20

I am very disappointed=20=20

ps: i am now thinking about switching to linux or windows.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243094-227-v9b7JNMK5H>