A heads-up to those thinking of installing/upgrading to
OpenBSD 3.2, and possible issues for other *nixes.

lpd/lpr permissions changed to use the group
daemon instead of the user daemon...

> -----Original Message-----
> From: Van Sickler, Jim [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 08, 2003 12:27 PM
> To: '[EMAIL PROTECTED]'
> Subject: checkpc vs 3.2 mini-FAQ
> 
> 
> If I use this snippet from the 3.2 upgrade mini-FAQ, checkpc -f
> complains about the rights on /var/spool/lpd as being
> 770 instead of 700, and changes the rights back to 700...
> 
> ##################################
> 
> 3.1.5: New permissions for lp* 
> The spool directories used by lpd must now be writable by
> group daemon in order for lpr to be able to spool files. 
> Additionally, the files within the spool directories must
> be owned by user and group daemon. This can be accomplished
> as follows: 
> 
>  # find /var/spool/output /var/spool/lpd -type d \
>       -execdir chgrp daemon {} \; -execdir chmod g+rwx {} \;
>  # find /var/spool/output /var/spool/lpd -type f \
>       -execdir chown daemon:daemon {} \;
> 
> #################################
> 
> So which/what needs to be fixed?
> 
changing spool_dir_perms=000700 in /usr/local/etc/lpd.conf
to spool_dir_perms=000770

fixes it...

Jim

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to