Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-14 Thread Gordon Messmer
Gustav Schaffter wrote: > I have later learnt that it might be smarter to REJECT calls to auth > than DENY'ing them. Should reduce number of retries and thereby shorten > any timeouts. Not really. As I was beginning to see earlier, when I wrote to the list regarding firewalls, REJECT is identica

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-14 Thread Gordon Messmer
Charles Galpin wrote: > 1. Like Gustav, I would like to know which is better I don't know. I don't get a high enough volume of auth requests on my mail servers to really care whether it's standalone or inetd. > 2. I did not have identd selected in ntsysv, and am quite sure I didn't > start it m

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-14 Thread Bret Hughes
> > > 2. I did not have identd selected in ntsysv, and am quite sure I didn't > > > start it mayself. So how did it get started? I'm thinking linuxconf is > > > trying to do it. If this is true, then maybe the simplest route is to run > > > it standalo

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-14 Thread Gustav Schaffter
sure I didn't > > start it mayself. So how did it get started? I'm thinking linuxconf is > > trying to do it. If this is true, then maybe the simplest route is to run > > it standalone and remove from inetd.conf. Anyone? > > > > On Mon, 13 Mar 2000, Gordon Messm

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-14 Thread Bret Hughes
rying to do it. If this is true, then maybe the simplest route is to run > it standalone and remove from inetd.conf. Anyone? > > On Mon, 13 Mar 2000, Gordon Messmer wrote: > > > Charles Galpin wrote: > > > Mar 13 22:49:24 server inetd[10663]: auth/tcp: bind: Address alre

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-14 Thread Charles Galpin
m thinking linuxconf is trying to do it. If this is true, then maybe the simplest route is to run it standalone and remove from inetd.conf. Anyone? On Mon, 13 Mar 2000, Gordon Messmer wrote: > Charles Galpin wrote: > > Mar 13 22:49:24 server inetd[10663]: auth/tcp: bind: Address already

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-14 Thread Gustav Schaffter
wrote: > > Mar 13 22:49:24 server inetd[10663]: auth/tcp: bind: Address already in > > use > > Mar 13 22:59:24 server inetd[10663]: auth/tcp: bind: Address already in > > use > > > > I have named setup to run at boot time in ntsysv. > > hehehe... The "

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-13 Thread Gordon Messmer
Charles Galpin wrote: > Mar 13 22:49:24 server inetd[10663]: auth/tcp: bind: Address already in > use > Mar 13 22:59:24 server inetd[10663]: auth/tcp: bind: Address already in > use > > I have named setup to run at boot time in ntsysv. hehehe... The "bind" in th

Re: inetd[10663]: auth/tcp: bind: Address already in use

2000-03-13 Thread Hal Burgiss
On Mon, Mar 13, 2000 at 11:04:13PM -0500, Charles Galpin wrote: > I know I've seen this one before, but can't find it in the archives > > I get these every ten minutes in the logs: > > Mar 13 22:49:24 server inetd[10663]: auth/tcp: bind: Address already in > use &g

inetd[10663]: auth/tcp: bind: Address already in use

2000-03-13 Thread Charles Galpin
I know I've seen this one before, but can't find it in the archives I get these every ten minutes in the logs: Mar 13 22:49:24 server inetd[10663]: auth/tcp: bind: Address already in use Mar 13 22:59:24 server inetd[10663]: auth/tcp: bind: Address already in use I have named setup

inetd[515]: auth/tcp : bind : address already in use

2000-02-26 Thread Fathi Ben Nasr
Hi,       I have upgraded to the latest lpd from priority.redhat.com and I still unable to print from anywhere. Telnetting to localhost 515 gives me "connection refused" and logs the subject of this message to /var/log/messages. Before the upgrade I was getting "malformed from address". I can

Re: bind: Address already in use (??)

1998-03-14 Thread Peter Chr. Hansen
This problem can also be because you have installed both gated and routed they are both programs that handles routing, but gated are mostly used in very big networks, so I would suggest that you remove the gated daemon. yours, Peter Chr. Hansen At 22:49 13-03-98 -0500, you wrote: >This is the sa

Re: bind: Address already in use (??)

1998-03-13 Thread GBNSCHBACH
This is the same one I get if I leave the system on overnight I just have not done any more researchI suspect in my case it is because I entered the DNS info during install, but did not build the bind databases yet. -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVE

RE: bind: Address already in use (??)

1998-03-12 Thread Joe Nestlerode
e> >Applixware directory structure for ".lock" files or something like that. > > > Joe Nestlerode wrote: > > After a rude reboot (power failure), I now get this when I try to start > > Applixware: > > > > kilgore ~>> applix & > >

RE: bind: Address already in use

1998-03-11 Thread Chuck Mead
> kilgore ~>> applix & > [1] 212 > kilgore ~>> bind: Address already in use > bind: Address already in use > connect: /usr/local/applix/axdata/axnet: Address already in use > [1]+ Exit 98 applix > kilgore ~>>

bind: Address already in use

1998-03-11 Thread Joe Nestlerode
After a rude reboot (power failure), I now get this when I try to start Applixware: kilgore ~>> applix & [1] 212 kilgore ~>> bind: Address already in use bind: Address already in use connect: /usr/local/applix/axdata/axnet: Address already in use [1]+ Exit 98