> It's always a user configuring something wrong or not RTFMing.
> Either setuiding lpr and friends or a force_localhost put somewhere
> fixes it.
Yeah... Use the Source, Luke, Use the Source.
>
> All stems from the force_localhost stuff, either the Debian package or
> LPRng in general changed the way this was handled.
>
> Another problem is due to me tightening up lpd.perms so remote users,by
> default, cannot access lpd. People don't read the READMEs.
>
> In any case Patrick, it's not really anything much you can fix, though
> perhaps when lpd starts it prints in nice big letters to all printers
> "I must read the READMEs".
>
> Speaking of remote access to lpd, people running Debian, if possible
> upgrade to lprng 3.6.24-3. -3 has the fix for that syslog overflow
> bug as mentioned on bugtraq.
Yes. Good idea.
>
> - Craig
> --
> Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
> Eye-Net Consulting http://www.eye-net.com.au/ <[EMAIL PROTECTED]>
> MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
