Bugzilla – Bug 113269
startpar remains with ial
Last modified: 2005-08-26 12:32:42 UTC
A startpar process remains after boot is finished. It seems always ial, which is the last started service. ps auxw | grep ial root 4955 0.0 0.3 4148 1524 ? S 12:41 0:00 /usr/sbin/iald root 4964 0.0 0.0 1520 452 ? Ss 12:41 0:00 startpar -f -- ial tiwai 5492 0.0 0.1 2736 692 pts/2 S+ 12:56 0:00 grep ial
Does the boot scsript of ial finish? Is the iald a real daemon which uses setsid(2)?
I've seen that $ rc$SERVICENAME {start|stop|restart} does not work for all services on Beta 4. For example: g0:~ # rccups status Checking for cupsd: running g0:~ # rccups stop Shutting down cupsd done g0:~ # rccups status Checking for cupsd: running
(In reply to comment #1) > Does the boot scsript of ial finish? > Is the iald a real daemon which uses > setsid(2)? No, it does not use setsid.
The program is not a real daemon and it seems not to close its file descriptors. IMHO the iald should be started with the startproc options -q and -s to get it to a real daemon.
I'm testing this right now.
Works fine, new package submitted.
Created attachment 47756 [details] just an other /etc/init.d/ial script You may consider this as rc.ial
Should I open a new bug for the disfunction of {stop|restart} for several services?
What do you mean with disfunction of {stop|restart} for several services? A resart including dbus and ial?
Takashi? Please could you test the new ial package in combination with startpar?
(In reply to comment #9) > What do you mean with disfunction of {stop|restart} for several services? > A resart including dbus and ial? No, I was referring to comment #2. Several services are not stopped on $ rc$SERVICENAME stop
See bug 113002
(In reply to comment #10) > Takashi? Please could you test the new ial package in combination > with startpar? mbuild trail-thoenig-3 (including werner's new rc.ial script)
Confirmed to be fixed. Thanks.