On 13.Oct.2000 -- 10:38 AM, [EMAIL PROTECTED] wrote:
> > From: Christian Haul <[EMAIL PROTECTED]>
> > Subject: LPRng hostname limit to 31 chars not suffiant
> >
> > Thanks for the great LPRng package. One thing though: in
> > src/include/lp.h the max length of a hostname is set to 31 according
> > to some RFC. I'm not into RFCs and thus I'm not going to do anything
> > about that RFC let alone know how to go about it. But at least here
> > this limit is way to restrictive:
> >
> > dortmund.dvs1.informatik.tu-darmstadt.de has 40 chars!
>
> You can use the 'shorthost' option to have only the first
> part of the hostname used.
>
> Sorry, but if you want RFC1179 compliance you need to use this.
>
> Now, of course, YOU can modify YOUR version of the source code
> and change this and compile a new version.
>
> >
> > Hence I'd like to suggest to extend this limit to something
> > larger. Attached you'll find a patch against 3.6.25 that extents it to
> > 255 char. Since I'm not clear on BRNAME I extended that one too.
>
> Nope. No can do. Not RFC1179 compliant.
>
Patrick, hope you don't mind if I take it to the mailing list but
since you seem to have subscribed me to it, I reckon it was your
intention anyway.
Let me answer this with some observations:
1) The field length is a maximum length, hence when your domain name
is compliant to the 31 char restriction nothing would change if
this limit was not enforced by LPRng anymore.
2) If your domainname does not conform to it, your printing services
a) will have been broken already, if your other printing software
enforces RFC1179.
b) will break when your previous software didn't enforce it but
LPRng does. (Solaris doesn't for example)
3) shorthost doesn't look like the right option if you need inter
domain printing (in our case e.g. from
dortmund.dvs1.informatik.tu-darmstadt.de to
printer12.rbg.informatik.tu-darmstadt.de )
4) LPRng HOWTO section 19: "This RFC is an informational RFC, which
means that the information in it is meant as a guide to users, and
not as a fixed standard."
5) I presume that this is not the first request on this matter. You
could make it a configuration option. Even more, since I guess that
case 2b) is not uncommon, configure could warn when the FQDN is >
31 chars that out-of-the-box LPRng could break the existing printing
subsystem.
6) Yes, I do patch new versions to accept longer FQDNs, but even when
using RPM for it it makes upgrades to new versions more
cumbersome. Nevertheless, it took some time to debug the behaviour
the first time. We could very well spare new users this hassle.
Cheers.
Chris.
--
Technische Universit�t Darmstadt +49.6151.16 -6232 (Tel) / -6229 (Fax)
Datenbanken & Verteilte Systems
http://www.informatik.tu-darmstadt.de/DVS1/staff/haul/
C h r i s t i a n H a u l PGP-Key:
http://www.informatik.tu-darmstadt.de/DVS1/staff/haul/pgp.html
[EMAIL PROTECTED] FPR: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856
335A 9E08
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
