Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30675 - [initscripts] remove daemon starting another daemon warning

Attached to Project: Arch Linux
Opened by Xyne (Xyne) - Saturday, 14 July 2012, 16:49 GMT
Last edited by Tom Gundersen (tomegun) - Sunday, 04 November 2012, 16:22 GMT
Task Type General Gripe
Category Packages: Core
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

/etc/rc.d/functions prints the following message when a daemon starts another daemon:
"A daemon is starting another daemon, this is unlikely to work as intended."

Why would it not work as intended? I have had no problems starting network-based daemons using POST_UP and PRE_DOWN with netcfg, for example. It's a bit annoying to have to see that message multiple times every time I start certain daemons.

Arch users are expected to know what they're doing, especially when doing uncommon things such as creating their own daemons. I see no need for extra hand-holding here. If it doesn't work as intended, the user will figure it out.

Yeah, you can just ignore the message, but it clutters the output and it is philosophically jarring.

Thanks.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Sunday, 04 November 2012, 16:22 GMT
Reason for closing:  Won't implement
Additional comments about closing:  If anyone wants this fixed, post a patch to the projects ml. I'm not going to be working on this.
Comment by Dave Reisner (falconindy) - Saturday, 14 July 2012, 17:05 GMT
Because it breaks on shutdown if there's an implicit ordering dependency. If a daemon is running but unlisted in /etc/rc.conf, it's shutdown first, possibly breaking the daemon that started it as a dependency.

If you want proper dependency handling, sysvinit/initscripts isn't going to do it.
Comment by Xyne (Xyne) - Saturday, 14 July 2012, 18:15 GMT
Why not stop the listed daemons first and then shut down whatever daemons are still running after that? That provides much more versatility.

The unlisted daemons are assumed to be independent so shutting them down last should work.

Comment by Tom Gundersen (tomegun) - Saturday, 21 July 2012, 21:51 GMT
@Xyne: the assumption is that if the daemon is not listed it was started manually after boot, so it should be shut-down before anything else.
Comment by Xyne (Xyne) - Sunday, 29 July 2012, 00:46 GMT
New proposal: instead of the nebulous and unhelpful "this is unlikely to work as intended" message, display "<daemon bar> will be stopped before <daemon foo> during shutdown", where <daemon foo> is the rc.conf daemon.
Comment by Tom Gundersen (tomegun) - Sunday, 29 July 2012, 01:08 GMT
@Xyne: I wouldn't be opposed to that. git formatted patches welcome at arch-projects@archlinux.org. Please sign up, and tag your Subject with [initscripts] to get through Pierre's filters ;-)
Comment by Xyne (Xyne) - Sunday, 29 July 2012, 05:34 GMT
Ok, I'll take a look at the code and see if I can submit a patch when I have the time.

Thanks.

Loading...