From: Vandevegt, James Matthew (Jim) (vandevegt@avaya.com)
Date: Thu Apr 22 2004 - 14:53:27 EDT
I've set up a Solaris 9 machine to house an application. Included in the setup
are a number of custom-written scripts which handle specialized printing
tasks. The script becomes the "interface" for the printer.
In most cases, my custom interface:
1) does some processing
2) (important part for this email) does some logging
3) submits a new print job to a "real" print driver that actually sends the
job to a printer.
Operationally, there's nothing wrong with any of my scripts. Everything
processes fine through them.
Here's my observation ... the processes executing the interface scripts are
owned by the user and group that submitted the print job. In other words, the
user that executed "lp -d<printer> ..." shows up as owning the process
running the interface. I really thought 'lp' was supposed to own those
processes.
Can anyone confirm or deny?
I've been unable to find any solid information on process ownership in the man
pages, admin guides, or on sunsolve. I'm curious if this behavior changed at
any particular Solaris version or patch level.
This behavior seems odd, because in order to accomplish my aforementioned
logging, I'll be forced to make my log files and directories wide open (mod
777) so any user can write to them. Any simple workarounds to this would be
most welcome as well.
As a side note, I realize that print jobs received from a remote system do
have all processes owned by 'lp' or whatever user name is specified in
inetd.conf.
Thanks for any insight,
Jim
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:28:31 EDT