:Update : :The socket /var/run/printer has permissions rwxrwx---. If I change them :to rwxrwxrwx there is no problem printing. : :Since no one else is complaining about this I assume I have something :set incorrectly but have run out of ideas. : :Thanks, Jim Chapman
Hmm. On my printer box that socket is 770 and I can print fine so I think changing the perms might just be masking the issue you are having. Usually printer daemon problems are due to ownership/group issues in /var/spool/lpd or /var/spool/output, or path specifications that are not accessible by group 'daemon'. backup# ls -la /var/spool/lpd total 2 drwxr-xr-x 2 root daemon 512 Sep 12 2005 . drwxr-xr-x 11 root wheel 512 Apr 2 2008 .. backup# ls -lRa /var/spool/output total 4 drwxr-xr-x 3 root daemon 512 Sep 22 10:57 . drwxr-xr-x 11 root wheel 512 Apr 2 2008 .. drwxr-xr-x 2 root daemon 512 Dec 1 10:23 lpd -rw-rw-r-- 1 root daemon 4 Dec 4 21:53 lpd.lock /var/spool/output/lpd: total 5 drwxr-xr-x 2 root daemon 512 Dec 1 10:23 . drwxr-xr-x 3 root daemon 512 Sep 22 10:57 .. -rw-r----x 1 root daemon 4 Sep 22 11:04 .seq -rw-rw-r-- 1 root daemon 33 Dec 1 10:23 lock -rw-rw-r-- 1 root daemon 25 Dec 1 10:23 status backup# In particular the lock file in /var/spool/output has to be 664 and the lock and status files in /var/spool/output/lpd have to be 664. And the group has to be 'daemon'. -Matt Matthew Dillon <dil...@backplane.com>