Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!utfyzx!harrison
From: harrison@utfyzx.UUCP
Newsgroups: comp.unix.questions
Subject: rsh and lp
Message-ID: <1987Mar3.063419.14477@utfyzx.uucp>
Date: Tue, 3-Mar-87 06:34:19 EST
Article-I.D.: utfyzx.1987Mar3.063419.14477
Posted: Tue Mar  3 06:34:19 1987
Date-Received: Tue, 3-Mar-87 18:40:31 EST
Reply-To: harrison@utfyzx.UUCP (David Harrison)
Organization: Dept. of Physics, Univ. of Toronto
Lines: 31

The environment: UNIX V.2 on an HP9000/500 (Release 5.11 of HP-UX).  
The users: 1400 undergraduates in a Physics teaching lab.  

The problem: we have our mostly naive users running under rsh(1) for 
their and our protection.  Whenever they send a job to lp(1) they 
get the message:
   sh: /dev/null restricted
The output comes out of the printer (a QMS Postscript PS800+ connected 
to a serial line) but the message is annoying.  

Not knowing where this message comes from, I'll try to be complete about
our configuration below.  I do know it is an artifact of rsh, because
only rsh users get it.

The port /dev/lp has been put to sleep by /etc/rc and then had its 
parameters set with a stty ... < /dev/lp.  Lp(1) is suid to owner 
lp, /dev/lp is mode crw------- and owned by lp, /dev/null is rw by 
the world.  Finally, the driver script in /usr/spool/lp/interface 
has the usual:
	for file in $files
	..
		/usr/local/lib/psf < "$file" 2>&1
	..
line where psf handles Postscript end-of-job stuff (and also converts 
a file not beginning wth "%!" to Postscript). 

Any ideas on how to get rid of this message?
Thanks in advance.
-- 
    David Harrison, Dept. of Physics, Univ. of Toronto
    {ihnp4,utzoo}!utgpu!utfyzx!harrison