perpetualrabbit,
indeed this looks unrelated to the upstart job. The problem with /etc/cups symlinks is that if you have one, cupsd seems to die immediately, and then upstart tries to start it again:
$ ls -ld /etc/cups* lrwxrwxrwx 1 root root 9 2011-05-25 10:13 /etc/cups -> cups.real drwxr-xr-x 4 root lp 4096 2011-05-25 10:00 /etc/cups.real
$ sudo strace cupsd -f [...] open("/etc/cups/cupsd.conf", O_RDONLY) = -1 EACCES (Permission denied) socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4 connect(4, {sa_family=AF_FILE, path="/dev/log"}, 110) = -1 ECONNREFUSED (Connection refused) close(4) = 0 exit_group(1) = ?
Now, I have no immediate idea why cupsd would get an EACCESS error on opening /etc/cups/cupsd.conf, I can even run it as non-root just fine:
$ head -n1 /etc/cups/cupsd.conf LogLevel warn
So this should be reported as a separate bug, preferably right at http://cups.org/str.php. Thanks!
perpetualrabbit,
indeed this looks unrelated to the upstart job. The problem with /etc/cups symlinks is that if you have one, cupsd seems to die immediately, and then upstart tries to start it again:
$ ls -ld /etc/cups*
lrwxrwxrwx 1 root root 9 2011-05-25 10:13 /etc/cups -> cups.real
drwxr-xr-x 4 root lp 4096 2011-05-25 10:00 /etc/cups.real
$ sudo strace cupsd -f etc/cups/ cupsd.conf" , O_RDONLY) = -1 EACCES (Permission denied) SOCK_CLOEXEC, 0) = 4
[...]
open("/
socket(PF_FILE, SOCK_DGRAM|
connect(4, {sa_family=AF_FILE, path="/dev/log"}, 110) = -1 ECONNREFUSED (Connection refused)
close(4) = 0
exit_group(1) = ?
Now, I have no immediate idea why cupsd would get an EACCESS error on opening /etc/cups/ cupsd.conf, I can even run it as non-root just fine:
$ head -n1 /etc/cups/ cupsd.conf
LogLevel warn
So this should be reported as a separate bug, preferably right at http:// cups.org/ str.php. Thanks!