Comment 7 for bug 1699065

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

In general the package has both upstart and systemd
$ dpkg -L sssd-common | grep init
/etc/init
/etc/init/sssd.conf
/etc/init/sssd-autofs.conf
$ dpkg -L sssd-common | grep service
/lib/systemd/system/sssd.service

#Checking the prerm
It calls service tasks via
1. if systemd installed /usr/bin/deb-systemd-invoke stop sssd.service
   That is a no-op on 14.404
2. if sysV or upstart script for sssd-autofs then
   invoke-rc.d sssd-autofs stop || invoke_failure
   This seems off by default (maybe no config), but the stop works
   $ service sssd-autofs status
   sssd-autofs stop/waiting
   $ invoke-rc.d sssd-autofs stop
   $ echo $?
   0
   So "ok" I think
2. if sysV or upstart script for sssd then
   invoke-rc.d sssd-autofs || invoke_failure
   The same as for sssd-auitofs
   $ service sssd status
   sssd stop/waiting
   $ invoke-rc.d sssd stop
   $ echo $?
   0

So all stops "work"
Maybe sssd needs to be up and running correctly before that to trigger the issue preferring the systemd service, checking that next.