It also happens if you set your permissions to secure in rc.config. Change rc.config to mode 644 and it'll work again. In secure mode it goes to 600 (I think, could be 640, anyway too secure for lpd ;-)) and the lpd can't read it anymore. Logical, since lpd runs under id lp. Stefan On Sun, 26 Nov 2000, Bo Jacobsen wrote:
I have a problem with harden_suse using SuSE70 that also was present in SuSE6.4:
After having run harden_suse (only saying yes to question 1, 2, 4 and 7) and editing /etc/rc.config making sure that lpd would run at startup, I was no longer able to print to my remote printserver.
Running undo_harden_suse did not help. The following error was found in /var/log/message: lpd: apsfilter: unable to print job .... nothing else.
I have tried to invoke lpd -f with the debug option but no aparent error messages apears.
!!------------------------------------------------------------- When I edit /etc/lpd.conf and changes user=lp to user=root it starts working again !!!?. !!-------------------------------------------------------------
If you know what the problem is please let me know.
Thanks in advance Bo Jacobsen bjc@image.dk
========================================== Stefan Suurmeijer Network Specialist University of Groningen tel: (++31) 50 363 3423 / 8258 fax: (++31) 50 363 7272 E-mail (business): s.m.suurmeijer@let.rug.nl or : s.m.suurmeijer@rc.rug.nl E-mail (private): stefan@symbolica.nl ========================================== Quidquid id est, timeo Microsoftum et dona ferentis (Whatever it is, I fear Microsoft, even when they are bringing gifts) The hardware requirements were Windows 95 or better, so I installed Linux