samba - May 1998 - SOLVED : (NEW Printing FAQ Question) : After almost every reboot, Samba printing is DOA under Solaris 2.6...

Ok.. Just a little follow-up on my Solaris printing problem that I was
having!
As it turns out, I put the fully-qualified path names to the print commands
(lpr/lpq/lprm, etc) in the samba config file (smb.conf) and all of my
printing
problems have disappeared!  Now, after a clean reboot of the OS (Solaris,
not PC), I can log on to Samba and directly print -- instead of it silently
failing!

Perhaps this should go in the FAQ?

Just for the record, I was NOT running Samba from inetd, but instead
starting
it via the Solaris /etc/rc2.d directory (equivalent to /etc/rc.local on
others)

-- Rick
-----Original Message-----
From: Rick Flower <Rick.Flower@trw.com>
To: Multiple recipients of list <samba@samba.anu.edu.au>
Date: Monday, May 11, 1998 9:18 AM
Subject: Re: After almost every reboot, Samba printing is DOA under Solaris
2.6...

>Ok.. I've taken your suggestion and changed the lpr commands so that
they
>fully
>specify the lpr commands (ie. "/usr/ucb/lpr" instead of just
"lpr" under
>Solaris 2.6).
>I've restarted Samba and it is working fine now -- so far.  I'll
keep an
eye
>on it and
>see if the problem is still lurking around after the next scheduled reboot
>(next Sunday).
>If the problem does go away, perhaps this needs to be put in the
>Printing.doc file.
>
>Also, we are starting our Samba from the /etc/rc2.d startup directory, and
>not from
>inetd.
>
>P.S.  Sorry about the Mime crud.. I didn't notice until the message
already
>went out
>        (and I got a copy of it through the list) that I sent it with
>Mime/HTML formatting.
>        I've rectified the situation and all of my listservs are now set
for
>plain-text only.
>
>
>>Actually, we've seen something like this under hpux, so I don't
think
>>it's related to your OS.
>>
>>>   print command  =3D lpr -r -P%p %s
>>
>>This could be your problem.  Put the full path for the lpr command in
>>here (e.g., /usr/sbin/lpr, or whatever it is for you).  When your
>>system reboots, it's probably not setting up the path for printing
>>adequately.  Are you restarting samba from inetd or from init.d?  (We
>>use init.d for our production machines, so that's where it happens
for
>>us).
>
>
>