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#9966 - NetworkManager service does not autostart hal but does dbus and dhcdbd

Attached to Project: Arch Linux
Opened by nothlit (nothlit) - Wednesday, 26 March 2008, 06:29 GMT
Last edited by Jan de Groot (JGC) - Friday, 14 November 2008, 22:36 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
/etc/rc.d/networkmanager start
starts dbus and dhcdbd if not running already, but not hal which it needs to find devices.
hal will start dbus and acpid on its own afaik


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 14 November 2008, 22:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in testing. This has been implemented upstream :)
Comment by James Rayner (iphitus) - Wednesday, 26 March 2008, 11:18 GMT
Start it yourself? dependency resolution for daemons was never a feature of the initscripts.
Comment by nothlit (nothlit) - Wednesday, 26 March 2008, 13:10 GMT
I would normally not mention it, but it autostarts those others. It would make sense to follow through, no?
Comment by Riri (chicha) - Wednesday, 14 May 2008, 12:14 GMT
Hello,

As long as it is explicitly documented to start hal before networkmanager on the related wiki page : http://wiki.archlinux.org/index.php/NetworkManager, this is not a bug, but a feature request.

I am requesting a closure and let the developer (Jan ?) decide whether he wants to turn this into a feature request or definitely close this request.

In case somebody is interested in my opinion (who knows ;-) ) : as long as initscripts are not made to handle dependencies I do not think this will be a good think to have this kind of feature : daemon A automatically starts daemon b and c ... I easily understand some exceptions such HAL starting DBUS and thus avoiding a big amount of daemons in the DAEMONS variable in rc.conf. But this should be an exception as long as daemons dependencies are not part of the initscript architecture.
Comment by James Rayner (iphitus) - Thursday, 15 May 2008, 08:06 GMT
I think this should be closed. Dependency resolution was _never_ part of the initscripts and should never have been included in the first place.

If someone wants to implement dependencies, it should be implemented properly, not ad hoc.
Comment by Jan de Groot (JGC) - Thursday, 15 May 2008, 09:22 GMT
Either have dependencies on all required services or have no dependencies at all. If this daemon makes users lazy because it starts dbus and dhcdbd, it should also start hal, or start none of these at all. I think I'll remove it from the next version and also from hal. Even Debian, the distro that patches and configures everything for you, doesn't include initscript dependencies other than starting individual initscripts in the right order at bootup.

Loading...