Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, Jul 23, 1999 at 02:29:19PM +0200, Sheldon Hearn wrote: Well, you did ask for them (inetd -l). :-) Jul 23 11:21:28 daemon.info printfix inetd[1743]: time from [...] Jul 23 11:21:28 daemon.info printfix inetd[1743]: daytime from [...] Usually syslog will give you "last message repeated X times". Unfortunately, the alternation of the messages makes this impossible. You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23 Jul 1999 13:50:45 +0100, David Malone wrote: You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... If, indeed, inetd is really "chewing CPU time". Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23-Jul-1999 at 13:50:45 +0100, David Malone wrote: On Fri, Jul 23, 1999 at 02:29:19PM +0200, Sheldon Hearn wrote: Well, you did ask for them (inetd -l). :-) Jul 23 11:21:28 daemon.info printfix inetd[1743]: time from [...] Jul 23 11:21:28 daemon.info printfix inetd[1743]: daytime from [...] Usually syslog will give you "last message repeated X times". Unfortunately, the alternation of the messages makes this impossible. You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... I think, I expressed myself wrong. Not the logging appears problematic but the fact that inetd seems to be stuck in an endless loop even long time after the nmap has finished. -Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, Jul 23, 1999 at 03:06:02PM +0200, Andre Albsmeier wrote: It's only nearly 50% because syslogd gets most of the other half :-) But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23-Jul-1999 at 14:16:19 +0100, David Malone wrote: On Fri, Jul 23, 1999 at 03:06:02PM +0200, Andre Albsmeier wrote: It's only nearly 50% because syslogd gets most of the other half :-) But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? Yes. I can still log in via the network and kill and restart inetd. Just found another syslog message (I didn't see it before because it disappeared in all the loge messages): Jul 23 15:20:51 daemon.err printfix inetd[5323]: chargen/udp server failing (looping), service terminated -Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23 Jul 1999 14:16:19 +0100, David Malone wrote: But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? Yeah. What we really need to know is how many packets inetd actually received. The manpage excerpt that DES showed us indicates that nmap doesn't stop sending packets immediately unless it gets an ICMP message back. We know that inetd doesn't send ICMP messages back. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, Jul 23, 1999 at 03:57:19PM +0200, Dag-Erling Smorgrav wrote: Andre Albsmeier [EMAIL PROTECTED] writes: Just to overcome speculations :-) I just tested it on another machine with the same result. If have tested it now between all 3 machines in each direction. Same result. Weird. I'm unable to reproduce it; my test box responds to UDP queries but does not log them (though it logs TCP queries). I'll update to the latest inetd and try again. I can reproduce it using version 1.63, ktracing shows: 3052 inetdCALL sigprocmask(0x1,0x82001) 3052 inetdRET sigprocmask 0 3052 inetdCALL sigprocmask(0x3,0) 3052 inetdRET sigprocmask 532481/0x82001 3052 inetdCALL gettimeofday(0xbfbfd5e4,0) 3052 inetdRET gettimeofday 0 3052 inetdCALL write(0xc,0xbfbfd60c,0x1a) 3052 inetdRET write -1 errno 39 Destination address required 3052 inetdCALL select(0x14,0xbfbfd750,0,0,0) 3052 inetdRET select 2 3052 inetdCALL sigprocmask(0x1,0x82001) 3052 inetdRET sigprocmask 0 3052 inetdCALL sigprocmask(0x3,0) 3052 inetdRET sigprocmask 532481/0x82001 3052 inetdCALL gettimeofday(0xbfbfd6f4,0) 3052 inetdRET gettimeofday 0 3052 inetdCALL write(0xe,0xbfbfd708,0x4) 3052 inetdRET write -1 errno 39 Destination address required 3052 inetdCALL sigprocmask(0x1,0x82001) 3052 inetdRET sigprocmask 0 3052 inetdCALL sigprocmask(0x3,0) 3052 inetdRET sigprocmask 532481/0x82001 It also seems to leave several hung processes around which are serveing disgard and echo. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, Jul 23, 1999 at 02:29:19PM +0200, Sheldon Hearn wrote: Well, you did ask for them (inetd -l). :-) Jul 23 11:21:28 daemon.info printfix inetd[1743]: time from [...] Jul 23 11:21:28 daemon.info printfix inetd[1743]: daytime from [...] Usually syslog will give you last message repeated X times. Unfortunately, the alternation of the messages makes this impossible. You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... David. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23 Jul 1999 13:50:45 +0100, David Malone wrote: You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... If, indeed, inetd is really chewing CPU time. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23-Jul-1999 at 13:50:45 +0100, David Malone wrote: On Fri, Jul 23, 1999 at 02:29:19PM +0200, Sheldon Hearn wrote: Well, you did ask for them (inetd -l). :-) Jul 23 11:21:28 daemon.info printfix inetd[1743]: time from [...] Jul 23 11:21:28 daemon.info printfix inetd[1743]: daytime from [...] Usually syslog will give you last message repeated X times. Unfortunately, the alternation of the messages makes this impossible. You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... I think, I expressed myself wrong. Not the logging appears problematic but the fact that inetd seems to be stuck in an endless loop even long time after the nmap has finished. -Andre To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, Jul 23, 1999 at 03:06:02PM +0200, Andre Albsmeier wrote: It's only nearly 50% because syslogd gets most of the other half :-) But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? David. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23-Jul-1999 at 14:16:19 +0100, David Malone wrote: On Fri, Jul 23, 1999 at 03:06:02PM +0200, Andre Albsmeier wrote: It's only nearly 50% because syslogd gets most of the other half :-) But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? Yes. I can still log in via the network and kill and restart inetd. Just found another syslog message (I didn't see it before because it disappeared in all the loge messages): Jul 23 15:20:51 daemon.err printfix inetd[5323]: chargen/udp server failing (looping), service terminated -Andre To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, 23 Jul 1999 14:16:19 +0100, David Malone wrote: But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? Yeah. What we really need to know is how many packets inetd actually received. The manpage excerpt that DES showed us indicates that nmap doesn't stop sending packets immediately unless it gets an ICMP message back. We know that inetd doesn't send ICMP messages back. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.
On Fri, Jul 23, 1999 at 03:57:19PM +0200, Dag-Erling Smorgrav wrote: Andre Albsmeier andre.albsme...@mchp.siemens.de writes: Just to overcome speculations :-) I just tested it on another machine with the same result. If have tested it now between all 3 machines in each direction. Same result. Weird. I'm unable to reproduce it; my test box responds to UDP queries but does not log them (though it logs TCP queries). I'll update to the latest inetd and try again. I can reproduce it using version 1.63, ktracing shows: 3052 inetdCALL sigprocmask(0x1,0x82001) 3052 inetdRET sigprocmask 0 3052 inetdCALL sigprocmask(0x3,0) 3052 inetdRET sigprocmask 532481/0x82001 3052 inetdCALL gettimeofday(0xbfbfd5e4,0) 3052 inetdRET gettimeofday 0 3052 inetdCALL write(0xc,0xbfbfd60c,0x1a) 3052 inetdRET write -1 errno 39 Destination address required 3052 inetdCALL select(0x14,0xbfbfd750,0,0,0) 3052 inetdRET select 2 3052 inetdCALL sigprocmask(0x1,0x82001) 3052 inetdRET sigprocmask 0 3052 inetdCALL sigprocmask(0x3,0) 3052 inetdRET sigprocmask 532481/0x82001 3052 inetdCALL gettimeofday(0xbfbfd6f4,0) 3052 inetdRET gettimeofday 0 3052 inetdCALL write(0xe,0xbfbfd708,0x4) 3052 inetdRET write -1 errno 39 Destination address required 3052 inetdCALL sigprocmask(0x1,0x82001) 3052 inetdRET sigprocmask 0 3052 inetdCALL sigprocmask(0x3,0) 3052 inetdRET sigprocmask 532481/0x82001 It also seems to leave several hung processes around which are serveing disgard and echo. David. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
