[00:31] Hi all! :) [00:32] We have a job script that is in a directory inside "/root" and we have a symlink pointing to it from "/etc/init" [00:32] But, for some reason, Upstart-related tools are unable to remember that the service exists across reboots. [00:33] We always end up having to do `initctl reload-configuration` [00:33] It's quite annoying [00:33] Does anyone know how to fix this? [00:34] By the way: LordShadowWing's copy of Upstart is the one affected [00:34] I'm just assisting him. [00:35] For those interested: [00:35] sudo ls -al ~root/.guix-profile/lib/upstart/system/guix-daemon.conf [00:35] -r--r--r-- 2 root root 351 Dec 31 1969 /root/.guix-profile/lib/upstart/system/guix-daemon.conf [00:37] ls -al /etc/init/guix-daemon.conf [00:37] lrwxrwxrwx 1 root root 55 Jan 8 14:19 /etc/init/guix-daemon.conf -> /root/.guix-profile/lib/upstart/system/guix-daemon.conf [00:40] LordShadowWing: I'll try reproducing your issue. [00:41] adfeno, I could give you ssh access [00:41] LordShadowWing: Don't worry... Let's see If I can test it from here. [00:41] ok [00:41] Wait a moment, have to reboot. [00:51] #upstart: We have decided to give ourselves some time on the matter. Thanks.: ) === JanC_ is now known as JanC [06:09] I've got an abandonware ubuntu 10.04 server here (upstat 0.6.5), and I'm trying to give its dovecot a higher nofiles limit. Do I need to explicitly tell upstart to reread /etc/init/foo.conf after I edit it (like "systemctl daemon-reload")? My memory says no, but I don't see any "init: reloading!" messages in syslog… [06:10] Ah initctl reload-configuration [06:11] slice init: Failed to spawn dovecot-inmate main process: unable to set "nofile" resource limit: Operation not permitted [06:11] Grargh [06:28] OK "limit nofile 9999 9999" worked, so maybe "limit nofile unlimited unlimited" is just not allowed [22:31] how I do I debug upstart hanging at boot time? I have managed to boot in bash, open a second shell and then exec'ed upstart