Re: tcp_wrapper in contrib and ports?

1999-06-07 Thread Dom Mitchell
On 7 June 1999, Ben Rosengart proclaimed: > I am curious as to why tcp_wrappers are present in /usr/src/contrib as > well as in the ports collection. Can someone please enlighten me? TIA. To support 2.2.x users? -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Always

Re: tcp_wrapper in contrib and ports?

1999-06-07 Thread Dan Langille
On 7 Jun 99, at 16:34, Dom Mitchell wrote: > On 7 June 1999, Ben Rosengart proclaimed: > > I am curious as to why tcp_wrappers are present in /usr/src/contrib as > > well as in the ports collection. Can someone please enlighten me? TIA. > > To support 2.2.x users? Yes. Please don't forget ab

Re: tcp_wrapper in contrib and ports?

1999-06-07 Thread Andrew Reilly
On Mon, Jun 07, 1999 at 04:34:53PM +0100, Dom Mitchell wrote: > On 7 June 1999, Ben Rosengart proclaimed: > > I am curious as to why tcp_wrappers are present in /usr/src/contrib as > > well as in the ports collection. Can someone please enlighten me? TIA. > > To support 2.2.x users? Maybe 3.x

Re: tcp_wrapper in contrib and ports?

1999-06-07 Thread Harlan Stenn
> My current source of confusion is with the tcpd from ports, > which doesn't mention what level it is syslogging at: I can't > find any of it's log messages... Try adding a '-v' to the syslogd startup (or '-vv'). Funny, that used to be documented in the man page... If that's not enough, add a

Re: tcp_wrapper in contrib and ports?

1999-06-08 Thread Dom Mitchell
On 8 June 1999, "Andrew Reilly" proclaimed: > Maybe 3.x users actually want tcpd too. I'm running -STABLE, and > qmail, and discovered that tcp_wrappers was somehow part of the > system when things started misbehaving. Oddly, tcpd itself is > _not_ built by the system, it seems. This is correc

Re: tcp_wrapper in contrib and ports?

1999-06-08 Thread Mikhail Teterin
Dom Mitchell once wrote: > This is correct; there is no need for it, as the support for the > wrappers was built directly into inetd. Check the CVS logs for inetd. Are not there any other uses for it? Like "xinetd"? If everything else (the libwrap, the man pages) is there, why not install

Re: tcp_wrapper in contrib and ports?

1999-06-11 Thread David O'Brien
> Are not there any other uses for it? Like "xinetd"? If everything else > (the libwrap, the man pages) is there, why not install the tcpd as well? BECAUSE IT IS NOT NEEDED by the base system. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@

Re: tcp_wrapper in contrib and ports?

1999-06-11 Thread Mikhail Teterin
David O'Brien once wrote: > > Are not there any other uses for it? Like "xinetd"? If everything > > else (the libwrap, the man pages) is there, why not install the tcpd > > as well? > > BECAUSE IT IS NOT NEEDED by the base system. It's Ok, no need to yell. There are a number of things, not