cucipop: unable to bind socket 110
Hi I run on my RH6.2 postfix+cucipop servers and yesterday, after an "electricity break" I rebooted and restarted all the servers and everything is working smoothly, exactly like it was before, but when I try to start cucipop I get "unable to bind socket 110" [failed] which is very strange because inetd can call cucipop with the exact same parameters succefully (I know that from the mail log and from the fact that I can retrieve my mail). Any ideas what's going on here ? And another general question: If everything is working (send+fetch+drac_auth etc.) should I be woried about somthing like that ? Ishai = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: cucipop: unable to bind socket 110
On Wed, 21 Feb 2001, Ishai Parasol wrote: Hi I run on my RH6.2 postfix+cucipop servers and yesterday, after an "electricity break" I rebooted and restarted all the servers and everything is working smoothly, exactly like it was before, but when I try to start cucipop I get "unable to bind socket 110" [failed] which is very strange because inetd can call cucipop with the exact same parameters succefully (I know that from the mail log and from the fact that I can retrieve my mail). Any ideas what's going on here ? And another general question: If everything is working (send+fetch+drac_auth etc.) should I be woried about somthing like that ? Ishai Did you run it as root? Only root can bind ports below 1024. Alon - if you cut here, you'll probably destroy your monitor -- This message was sent by Alon Altman ([EMAIL PROTECTED]) ICQ:1366540 The RIGHT way to contact me is by e-mail. I am otherwise nonexistent :) = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: cucipop: unable to bind socket 110
Sure. - Original Message - From: "Alon Altman" [EMAIL PROTECTED] To: "Ishai Parasol" [EMAIL PROTECTED] Cc: "Linux - IL Maling List" [EMAIL PROTECTED] Sent: Wednesday, February 21, 2001 11:50 AM Subject: Re: cucipop: unable to bind socket 110 On Wed, 21 Feb 2001, Ishai Parasol wrote: Hi I run on my RH6.2 postfix+cucipop servers and yesterday, after an "electricity break" I rebooted and restarted all the servers and everything is working smoothly, exactly like it was before, but when I try to start cucipop I get "unable to bind socket 110" [failed] which is very strange because inetd can call cucipop with the exact same parameters succefully (I know that from the mail log and from the fact that I can retrieve my mail). Any ideas what's going on here ? And another general question: If everything is working (send+fetch+drac_auth etc.) should I be woried about somthing like that ? Ishai Did you run it as root? Only root can bind ports below 1024. Alon - if you cut here, you'll probably destroy your monitor -- This message was sent by Alon Altman ([EMAIL PROTECTED]) ICQ:1366540 The RIGHT way to contact me is by e-mail. I am otherwise nonexistent :) = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: cucipop: unable to bind socket 110
netstat gives: tcp 0 0.0.0.0.0:110 0.0.0.0:*LISTEN - Original Message - From: "Tzafrir Cohen" [EMAIL PROTECTED] To: "Ishai Parasol" [EMAIL PROTECTED] Sent: Wednesday, February 21, 2001 11:52 AM Subject: Re: cucipop: unable to bind socket 110 On Wed, 21 Feb 2001, Ishai Parasol wrote: Hi I run on my RH6.2 postfix+cucipop servers and yesterday, after an "electricity break" I rebooted and restarted all the servers and everything is working smoothly, exactly like it was before, but when I try to start cucipop I get "unable to bind socket 110" [failed] which is very strange because inetd can call cucipop with the exact same parameters succefully (I know that from the mail log and from the fact that I can retrieve my mail). Any ideas what's going on here ? And another general question: If everything is working (send+fetch+drac_auth etc.) should I be woried about somthing like that ? What do you mean by 'everything working'? Anybody listening on port 110? netstat -l --ip -n |grep 110 fuser -v -n tcp 110 whatever -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: 110
- Original Message - From: "Tzafrir Cohen" [EMAIL PROTECTED] To: "Ishai Parasol" [EMAIL PROTECTED] Sent: Wednesday, February 21, 2001 12:29 PM Subject: Re: cucipop: unable to bind socket 110 Is it supposed to listen on port 110, or be called by inetd ? fuser -v -n tcp 110 will tell you which process listens on port 110. I'm not sure. what's the difference between those two (regarding to 110) If inet listens and "calls" cucipop every time it get a "110 call" why do i need cucipop to listen on 110 too ? I don't have fuser file on my system. where can I get it ? Thaks, Ishai = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: 110
On Wed, Feb 21, 2001 at 01:04:25PM +0200, Ishai Parasol wrote: I'm not sure. what's the difference between those two (regarding to 110) If inet listens and "calls" cucipop every time it get a "110 call" why do i need cucipop to listen on 110 too ? If cucipop runs as an inetd application, it would interface with inetd (via STDIN / STDOUT) for it's network IO. Maybe cucipop cannot detect it's in inetd mode automatically, so you got to configure it not to run in 'standalone mode'. I don't have fuser file on my system. where can I get it ? On Debian, I have it in package 'psmisc'. 'lsof' (LiSt Open Files) is also a nice tool to have for those purposes. -- Best regards, Ilya Konstantinov = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
