insserv does not work when rsync or winbind are installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
insserv (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Lucid Alpha 3 (updated to latest today).
When rsync or winbind are installed insserv fails to process any init scripts. There is a lot of warnings outputted about LSB tags, overrides and Upstart it all ultimately ends with:
insserv: There is a loop between service rsyslog and rsyncd if stopped
insserv: loop involving service rsyncd at depth 3
insserv: loop involving service rsyslog at depth 2
insserv: loop involving service udev at depth 1
insserv: There is a loop between service rsyncd and rsyslog if stopped
insserv: exiting now without changing boot order!
This loop problem is the real error and insserv refuses to do anything. Getting rid of /etc/init.d/rsync or /etc/init.d/winbind makes the problem go away and then insserv works.
affects: | ubuntu → insserv (Ubuntu) |