From owner-freebsd-hackers Tue Sep 22 06:03:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27491 for freebsd-hackers-outgoing; Tue, 22 Sep 1998 06:03:06 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27485 for ; Tue, 22 Sep 1998 06:03:05 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id GAA22448; Tue, 22 Sep 1998 06:02:25 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id GAA22484; Tue, 22 Sep 1998 06:02:24 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id GAA17355; Tue, 22 Sep 1998 06:02:23 -0700 (PDT) From: Don Lewis Message-Id: <199809221302.GAA17355@salsa.gv.tsc.tdk.com> Date: Tue, 22 Sep 1998 06:02:23 -0700 In-Reply-To: Greg Lehey "The inetd realloc problem: an observation" (Sep 22, 1:44pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Greg Lehey , FreeBSD Hackers Subject: Re: The inetd realloc problem: an observation Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 22, 1:44pm, Greg Lehey wrote: } Subject: The inetd realloc problem: an observation } I trust that everybody knows what I mean by the "inetd realloc" } problem: after some undefined event inetd behaves in an unfriendly } manner towards incoming requests, possibly confusing the clients } enough to make them turn away in disgust. I'm can't say I'm suprised after looking at the code, which does all sorts of dangerous things like malloc() from within signal handlers. There are some things it is safe to do within a signal handler, but most things aren't. Probably the best thing to do is to rewrite the code so that the signal handlers just set a flag (of type sig_atomic_t), which gets checked in the mainline code where it is safe to to the complicated stuff. } This happened to me again } today, and I restarted inetd. I've found that every time I do this, I } get the following message at regular intervals: } } Sep 22 13:37:00 freebie inetd[12206]: netbios-ns/udp: bind: Address already in use } } Now I don't use any such service, nor is there any entry for it in } inetd.conf. Where is this coming from? Sure, this is the new inetd, } not the old one, but it's puzzling that this happens every time. There's an entry for this at the bottom of my inetd.conf, but it's commented out. # Enable the following two entries to enable samba startup from inetd # (from the Samba documentation). # #netbios-ssn stream tcp nowait root /usr/local/sbin/smbd smbd #netbios-ns dgram udp wait root /usr/local/sbin/nmbd nmbd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message