reassign 636054 sysvinit-utils thanks On lun., 2011-08-01 at 10:51 +0200, Yves-Alexis Perez wrote: > On sam., 2011-07-30 at 12:14 -0300, Fernando Tarlá Cardoso Lemos wrote: > > I think the problem is that the lightdm package installs an upstart > > init > > script. /usr/sbin/service thinks upstart is available and fails to > > start > > lightdm: > > > > fernando@munchkin:~$ sudo service openntpd restart > > Restarting openntpd: ntpd. > > fernando@munchkin:~$ sudo service lightdm restart > > exec: 129: restart: not found > > fernando@munchkin:~$ > > > > I guess this bug could also have been filed against sysvinit-utils, > > but > > on the other hand, I'm not sure we're supposed to be shipping upstart > > init files yet. The "service" utility has no problem whatsoever with > > packages that ship systemd init files (and it works with systemd), but > > seems to choke on upstart init files. > > I've taken the time to look a bit more at this and I'm wondering. Why do > you think this has anything to do with /etc/init/lightdm? > > 'service' seems to try to execute 'restart' instead of calling the right > script with argument, but that looks completely unrelated to upstart > files.
Replying to myself: because 'service' has a compatibility layer for
upstart which I don't get at all:
----
if [ -r "/etc/init/${SERVICE}.conf" ]; then
# Upstart configuration exists for this job
case "${ACTION}" in
start|stop|restart|status|reload)
# Action is a valid upstart action
exec ${ACTION} ${SERVICE} ${OPTIONS}
;;
force-reload)
# Upstart just uses reload for force-reload
exec reload ${SERVICE} ${OPTIONS}
;;
esac
fi
----
How could that even work? I think it misses ${SERVICE} before ${ACTION}
or something.
Reassigning then.
Regards,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pkg-xfce-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-xfce-devel
