Re: tcp_wrapper in contrib and ports?
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...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
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 needed by the system, that are in the system. Not just the fortran and xtend, but also, say, bc(1) or cal(1). It may be usefull, and it requires no effort to have -- in fact, it probably needed some effort to be ripped out. But most importantly, it is hard to _add_ gracefuly to an installed system. Porter will have to work hard to make the tcp_wrapper port work with the system libwrap, while having two libwrap-s is just plain ugly. -mi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
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 correct; there is no need for it, as the support for the wrappers was built directly into inetd. Check the CVS logs for inetd. The libwrap that is built (or at least the man page for tcpdchk) seems to think that the control files hosts.access and hosts.deny still live in /usr/local/etc/, rather than where you would expect a system component to put them: /etc. My tcpdchk doesn't seem to have this problem; then again, I'm running -CURRENT. Maybe you have a version left over from the ports? Try seeing what order your MANPATH is set or doing man -d tcpdchk. 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... I find that it's convenient to redirect all logging to a spare VT: [ /etc/syslogd.conf ]--- ... *.* /dev/ttyv7 That always lets you see what's going on. -- Dom Mitchell -- Palmer Harvey McLane -- Unix Systems Administrator Always think very hard before messing with TCP. And then don't. -- MC -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
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 the tcpd as well? -mi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
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 think very hard before messing with TCP. And then don't. -- MC -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
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 about us! [using 2.2.8 and 3.1] -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
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 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. The libwrap that is built (or at least the man page for tcpdchk) seems to think that the control files hosts.access and hosts.deny still live in /usr/local/etc/, rather than where you would expect a system component to put them: /etc. 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... -- Andrew To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
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 '-d' so you can watch what happens. It shouldn't take long to find what you want. Checking the source, it looks like it uses LOG_MAIL as the facility. You can also use the ! stuff in syslog.conf - the tcp wrappers use the invoking program name to log stuff. H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
