topic Re: Users Cannot Print...But root can... in Operating System - HP-UX

Users Cannot Print...But root can...

jmckinzie — Mon, 27 Mar 2006 11:18:51 GMT

I am having a problem. My users cannot print at all however, root can print just fine.

When I print from root, I get:

# banner "TEST"|lp -d G1B013_J4
request id is G1B013_J4-28 (standard input)

When I print from any other user i get:

banner "TEST"|lp -d G1B013_J4
#

Re: Users Cannot Print...But root can...

Steven E. Protter — Mon, 27 Mar 2006 11:30:56 GMT

Shalom Jody,

Check file permissions on the lp program. You may need sudo to give full rights to non-root users, but should not have to go that far.

SEP

Re: Users Cannot Print...But root can...

A. Clay Stephenson — Mon, 27 Mar 2006 11:31:52 GMT

This is almost always caused by changing the mode of critical lp files --- often by removing the setuid bit. For example, lp must be 4555 and owned by root:bin. lpsched must also be 4755 and owned by root bin. You also should look at the permissions of the directories and files under /var/spool/lp. The easist way is to compare the modes and ownerships of the files on a good system with your bad system.

This often happens when a system has been "improved" to meet security audit requirements without a thorough understanding of the underlying subsystems like lp.

You may get some clues by examining /var/spool/lp/log.

Re: Users Cannot Print...But root can...

Bill Hassell — Mon, 27 Mar 2006 19:28:35 GMT

As Clay mentions, permissions and ownership are correct out of the box and 'improvements' almost always break things, especially when generalized rules for multiple OS's are used. You can verify all the files and executables for your spooler using swverify. Just tell it to verify the lp spooler product. The name depends on the version of HP-UX you are using.

Re: Users Cannot Print...But root can...

jmckinzie — Thu, 31 Jan 2008 16:17:38 GMT

Found the solution....but, honestly cannot remember what it was (Look at dates)