Bug 7226
| Summary: | lpr 0.46 printing fails "was not linked to the original file" | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | allbery |
| Component: | lpr | Assignee: | Bernhard Rosenkraenzer <bero> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.2 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-01-19 14:14:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Can't reproduce it here - but I'll have a look at the source. In the meantime, can you try the 0.47 version from rawhide? The problem appears to be that the required permissions on /var/spool/lpd/* changed from what we have been using on Linux and other platforms. The randomness of the group IDs acquired by lpd is still perplexing but we can live with it. Should be fixed in 0.50 |
Printing with lpr 0.46 fails with: (example) Subject: tolkien printer job "<unknown>" Date: Mon, 22 Nov 1999 00:35:52 -0500 From: bin <bin.cmu.edu> Reply-To: root.cmu.edu Your printer job was not printed because it was not linked to the original file This does not happen on all systems (yet), but once it starts happening it happens for all print jobs to all printers and can only be worked around by allowing world read and search access to /var/spool/lpd/* (which raises security issues). strace'ing lpd reveals that the daemon spawned to process queue jobs is doing setregid(-1, <random group ID>); setreuid(-1, <owner of print job>); The group ID is random in the sense that a different group ID is "chosen" every time lpd is restarted; if it happens to use the correct group ID 2(daemon) then printing will work until lpd is again restarted.