Date: Sat, 1 Nov 2003 00:35:57 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: <MPAREDES@telmex.com> Cc: FreeBSD-Questions@freebsd.org Subject: RE: problems with LPD Message-ID: <p06002027bbc8f4376f1a@[128.113.24.47]> In-Reply-To: <E3F56D7842656F4484C5668BC4D7F298042B63@is~tmxmailhmo1.intranet.telmex.com > References: <E3F56D7842656F4484C5668BC4D7F298042B63@is~tmxmailhmo1.intranet.telmex.com >
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:55 PM -0700 10/31/03, <MPAREDES@telmex.com> wrote:
>Hi Garance.
>
>Thanks for your answer, ...
>I think that the solution to my dilemma, is modify
>the source code of LPD.
>
>But before this I like to try the "netgroup" option,
>where can I begin to read?
Well, you can check:
man hosts.lpd
which will tell you almost nothing. Now it happens that
the hosts.lpd is actually processed by the same code that
handles hosts.equiv, although that is not documented. So,
it happens to be true that:
man hosts.equiv
will tell you some additional hints as to what is available.
However, you will notice that the man page for hosts.equiv
does little more than point you to the source code. So,
that is not very helpful either.
There is also:
man netgroup
which will tell you the format of the /etc/netgroup file. I
should mention that I have never actually used netgroups, so
I am not sure that they will help you in this case.
I have skimmed through all of the above, and my guess is that
your original idea is probably the easiest one to do. It
should be easier to change the source code in lpr/lpd/lpd.c
to make it behave the way you want it to behave. Now that
I have read more about netgroups, I expect that they are not
very useful for what you really want to do.
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06002027bbc8f4376f1a>