Hello Felix,
Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> writes: > Hi, > > My timer join-irc-channels [1] starts when being 'deployed' but is gone > after a reboot, even though the Shepherd configuration includes a > reference to it. [2] There is no trace: > > # herd status join-irc-channels > herd: error: service 'join-irc-channels' could not be found > > The system generation was updated properly. Any ideas are welcome. I think you should see an exception in /var/log/messages, or there really isn't anything? I tried to get parts of your operating system (didn't want to build the whole thing) and I am getting unbound variable for make-timer-constructor. (Since I don't have the whole system this could be potentially other error than your actual one. On the other hand I really think this is it - see next paragraph) This is because the %default-modules[1] of shepherd-service do not contain (shepherd service timer) which has make-timer-constructor. It's strange it works for you on reconfigure and not boot though. Maybe the module is loaded somewhere in the running shepherd proces... I am not sure if this is an oversight on guix channel side, or if the timers module really shouldn't be in hte default modules... > > P.S. Do I need to start services explicitly when they appear in > another's 'requirements'? Nope, because shepherd starts all services (unless you set auto-start of them to #f) in correct order according to requirements. Regards, Rutherther PS I think that the help-guix mailing list is better suited for questions about problems. [1] gnu/services/shepherd.scm (%default-modules)
