From owner-freebsd-bugs@freebsd.org Sun Jan 5 19:37:55 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 564B91E3E31 for ; Sun, 5 Jan 2020 19:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47rTSg1jSQz4g37 for ; Sun, 5 Jan 2020 19:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 38E5E1E3E30; Sun, 5 Jan 2020 19:37:55 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 38ADF1E3E2F for ; Sun, 5 Jan 2020 19:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47rTSg0p7Gz4g36 for ; Sun, 5 Jan 2020 19:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 16F352665 for ; Sun, 5 Jan 2020 19:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 005Jbspl040994 for ; Sun, 5 Jan 2020 19:37:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 005JbsiZ040993 for bugs@FreeBSD.org; Sun, 5 Jan 2020 19:37:54 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 243094] reboot problem Date: Sun, 05 Jan 2020 19:37:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: bernhard@blberger.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jan 2020 19:37:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243094 --- Comment #6 from Bernhard Berger --- (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.=