Bug#736258: acpid won't stop, won't upgrade (systemd) - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736258

ZH $ sudo systemctl stop acpid ZH Job for acpid.service canceled. ... because, as noted, it's a socket-activated service, which actually makes it two separately startable and stoppable things (acpid.service and acpid.socket) in the world of systemd, only one of which is being stopped when you're

Bug#741930: Re: Bug#741930: reportbug: add current init system information

Sandro Tosi: what is the recommended way to identify sysvinit? from the info provided above one requires to check a dir existence and the checking a command and then execute it to parse its output. it seems a bit fragile, and maybe only upstart check really the running processes There

Bug#825394: systemd kills background processes after user logs out

Martin Pitt: > The option has already be reverted in the packaging git. > This isn't an exercise in "who shouts the loudest". It should, however, be an exercise in fixing bugs properly. (-: Turning off the enabling flag doesn't fix the underlying flawed mechanism. There is still a logind bug

Bug#815834: mdadm: with systemd as PID 1, no clean way to restart the mdadm monitor

Francesco Poli: Please help me understand, in case I am completely off-track. You are off-track. This is not an mdadm bug. There is nothing to fix in mdadm for this. This is not a systemd bug. There is nothing to fix in systemd for this, either. Francesco Poli: Unfortunately,

Bug#890810: Handling of symbolic links has been broken

(My apologies for the late reply. Your mail never arrived, and I only discovered it on the WWW interface yesterday.) Thorsten Glaser: I’ve noticed an error (in the native BSD environment) which I believe to be related, if not the same, but haven’t gotten around to debugging yet. I’ll have

Bug#889144: systemd 237-1: problem starting dnsmasq

Michael Biebl: If other services depend on dnsmasq, please keep https://www.lucas-nussbaum.net/blog/?p=877 in mind Please do not. It is an erroneous conclusion based upon a faulty analysis that conflates the readiness protocols

Bug#890810: Handling of symbolic links has been broken

Package: pax Version: 1:20161104-2 pax is incorrectly using utimes() to attempt to set the timestamps of symbolic links, rather than utimensat() with AT_SYMLINK_NOFOLLOW. $ install -d -m 0755 a b $ ln -s /etc/motd a/c $ cd a $ pax -r -w * ../b/ pax: Access/modification time set failed on:

Bug#888270: Oracle's naming scheme has changed with Java 1.9 breaking make-jpkg

Package: java-package Version: 0.56 $ make-jpkg serverjre-9.0.1_linux-x64_bin.tar.gz Creating temporary directory: /tmp/make-jpkg.T2DwKXL7lO Loading plugins: /usr/share/java-package/common.sh /usr/share/java-package/javase.sh /usr/share/java-package/jdk-doc.sh /usr/share/java-package/jdk.sh

Bug#881490: sysvinit-core: shutdown should default to -h

Jesse Smith: 881490 (Feature requests asks that, when user provides no valid action for shutdown that we immediately power off, killing any running processes. This sounds terrible/dangerous and we will not implement it upstream. Report can be closed.) This is a wildly inaccurate

Bug#586709: closed by Thomas Goirand

/etc/init.d/halt is an rc script. It does not have a specific manual page, and its command-line usage is that of all other van Smoorenburg rc scripts, namely one of the conventional start|stop|try-restart|status verbs as a single second argument. This is documented in chapter 9 of the Debian

Bug#746442: Please make /etc/rc.local non-executable by default

KatolaZ: /etc/rc.local is expected to be executed by rc at the end of each multiuser runlevel. [...] Removing the +x bit will break it immediately, and to no avail. There is a bit of a myth that has grown up about /etc/rc.local in recent years, that it was executed "last". *

Bug#746442: Please make /etc/rc.local non-executable by default

Josh Triplett: (Personally, I *wish* that /etc/rc.local didn't exist at all by default and you had to *create* it if you wanted it used.) So too did Lennart Poettering. * https://bugzilla.redhat.com/show_bug.cgi?id=734268 Matthew Dillon went a step further, and deleted /etc/rc.local from

Bug#746442: Please make /etc/rc.local non-executable by default

Thorsten Glaser: I would be massively surprised if I installed a system, added something to rc.local, and it were not run. You would be massively surprised on Arch Linux and its derivatives, then. systemd is built without its backwards compatibility mechanisms on Arch, and /etc/rc.local

Bug#718416: Debian Bug#718416: closed by Dmitry Bogatov

Benda Xu: As you said Psst! You are conflating two different people whose names start with "T". (-: The world really does want one to clean one's screen, and there are multiple layers of stuff to unpick if one does not want to do so. * https://unix.stackexchange.com/a/233855/5132

Bug#916230: Log rotation issue with runit

Dmitry Bogatov: After some investigation I found code, that caused issue, but it seems that it was written with some purpose, yet I fail to understand that purpose. What you need are manuals that tell you about this mechanism. (-: *

Bug#917105: urxvtd and urxvtc: enhance to interoperate with service managers

Package: rxvt-unicode Version: 9.22-1+b1 |urxvtd| can be run as a per-user service under the nosh toolset's service manager and under systemd. It does not have the problems that some X11 terminal emulators have with needing a |DISPLAY| environment variable in the dæmon. But it is not

Bug#917105: urxvtd and urxvtc: enhance to interoperate with service managers

This is also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234276 .

Bug#917100: setterm: specifying default colours is broken

Package: util-linux Version: 2.29.2-1+deb9u1 % setterm --foreground default --background default|hexdump -C 1b 5b 33 29 6d 1b 5b 34 29 6d |.[3)m.[4)m| 000a % Those closing bracket characters should be '9's.

Bug#822753: /lib/init/init-d-script: exit 0 at end of script prevents all other exit codes

Michael Biebl: fwiw, this is why I suggested to provide a C implementation of init-d-script which can be used as an interpreter That's how it was addressed in 2007. * https://github.com/OpenRC/openrc/commit/5af58b45146ab5253ca964738f4e45287bf963d4 *

Bug#822753: /lib/init/init-d-script: exit 0 at end of script prevents all other exit codes

Dmitry Bogatov: I believe I already wrote in init-d-script(5) correct invocation: #!/usr/bin/env /lib/init/init-d-script That's not what was in the skeleton that you just got rid of; which had more attention paid to it than the example in the manual page had, I suspect. The next

Bug#822753: /lib/init/init-d-script: exit 0 at end of script prevents all other exit codes

Dmitry Bogatov: Can you please elaborate, what exactly would break? Look at the way that the init-d-script script is used. It isn't used as the interpreter of an rc script. (Your manual needs fixing to show the correct way to invoke it, by the way.) It is invoked as: #!/bin/sh if [

Bug#799329: sysvinit: does not work inside systemd-nspawn

Dmitry Bogatov: Can we expect you [Andreas Henriksson] to provide necessary lines in /etc/inittab? Xe will have some difficulty doing that completely. The systemd protocol for such containers is to have a fixed TUI login service on /dev/console (as already mentioned) and *also*

Bug#567071: what is the purpose of fstab-decode

Dmitry Bogatov: > What exactly is decoded? Where should I read about escaping rules? How it is different from plain `xargs'? You are suffering from the notoriously poor Linux documentation. (-: The manuals for fstab on the BSDs explain that the fields are encoded , so that they can contain

Bug#567071: what is the purpose of fstab-decode

Dmitry Bogatov: > Also, reference to fstab(5) and this particular paragraph may be useful: Not as much as you would think. The idiosyncratic encoding applies to more than just that 1 field, and encodes more than what is stated, but does not generalize to octal escaping as one might guess.

Bug#633858: -v not as safe as it sounds

Jesse Smith: > I think the manual page is correct Clearly it is not, otherwise you would not yourself in the same breath have to employ a different explanation: > The -v command only turns on verbose messages, The manual page does not say this. It says "Write out what is currently going

Bug#132542: sysvinit: please make /etc/init.d/rcS a conffile

Pierre Ynard: > udev (not even original systemd software) [...] (and unlike init, there's no alternative to it) The Devuan people would like to introduce you to vdev . Laurent Bercot would like to introduce you to mdevd

Bug#132542: sysvinit: please make /etc/init.d/rcS a conffile

Thorsten Glaser: > Just accept that this idea, originating from the systemd people at Fedora/Freedesktop, is NOT welcome to classical Unix people. Ahem! We classical Unix people experienced this idea in the late 1980s, from where it *really* originated, Sun and AT *