From: D-Nice <D-Nice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Since runit update, previous power down commands reboot the system now
Date: Mon, 10 Aug 2020 22:36:55 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24207@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
New issue by D-Nice on void-packages repository
https://github.com/void-linux/void-packages/issues/24207
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.7.14_1 x86_64 GenuineIntel notuptodate hold rrDDDDFFFF`
* package:
`runit-void-20200720_1.x86_64`
### Expected behavior
`poweroff`, `shutdown`, `halt`, with the appropriate flags to lead to a power down, or in the case of touching the power button, as previously, to lead to a power down.
### Actual behavior
All those commands an actions lead to a reboot, and the final init message indicates a reboot was requested.
### Steps to reproduce the behavior
`sudo poweroff` with aforementioned pkg, at least on my system.
Reverting to `runit-void-20190906_3.x86_64` stops this from happening, and there were apparent changes done to how runit handles reboots, but turning everything into a reboot for me does not seem like a desired effect.
Revelant PR: https://github.com/void-linux/void-packages/pull/23668
Additional info:
`runit-void-20190906_3.x86_64` - `ls -l /run/runit/{reboot,stopit}` output:
```
ls: cannot access '/run/runit/reboot': No such file or directory
---x------ 1 root root 0 Aug 10 16:22 /run/runit/stopit
```
`runit-void-20200720_1.x86_64` - `ls -l /run/runit/{reboot,stopit}` output:
```
TODO in edit after re-update
```
next reply other threads:[~2020-08-10 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 20:36 D-Nice [this message]
2020-08-10 20:46 ` ericonr
2020-08-10 20:49 ` D-Nice
2020-08-10 20:50 ` ahesford
2020-08-10 21:01 ` D-Nice
2020-08-10 21:01 ` [ISSUE] [CLOSED] " D-Nice
2020-08-10 21:03 ` ericonr
2020-08-10 21:11 ` D-Nice
2020-08-10 21:15 ` ericonr
2020-08-10 21:20 ` D-Nice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24207@inbox.vuxu.org \
--to=d-nice@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).