From owner-freebsd-questions Thu Jul 4 21:44:58 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52ED337B400 for ; Thu, 4 Jul 2002 21:44:56 -0700 (PDT) Received: from stjohn.stjohn.ac.th (stjohn.stjohn.ac.th [202.21.144.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F50443E09 for ; Thu, 4 Jul 2002 21:44:53 -0700 (PDT) (envelope-from mcrogerm@stjohn.ac.th) Received: from tulip ([203.151.134.104]) by stjohn.stjohn.ac.th (8.9.3+Sun/8.9.3) with SMTP id VAA02675 for ; Thu, 4 Jul 2002 21:44:11 -0700 (GMT) Message-Id: <3.0.6.32.20020705114443.007aa820@stjohn.stjohn.ac.th> X-Sender: mcrogerm@stjohn.stjohn.ac.th X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 05 Jul 2002 11:44:43 +0700 To: freebsd-questions@FreeBSD.ORG From: Roger Merritt Subject: Disappearing Daemon? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've posted this question before under the subject, "Samba disappears", but perhaps the subject title made it seem like the question was specifically about Samba. I don't think that's it. Something is causing the process to vanish after it's been started. For the last couple of weeks (I'm not sure when it started) I've been having a problem running Samba. The program is started as a daemon on boot-up, but then the process seems to disappear. I've tried starting it manually, and the same thing happens. It's baffling, because it had been running fine for the last three or four years. I can't figure out what changed on the server, but something must have. I'm running Freebsd 4.5-STABLE: FreeBSD 4.5-STABLE FreeBSD 4.5-STABLE #0: Wed Feb 27 08:29:05 ICT 2002 and have upgraded to Samba 2.2.5, but the behavior was observed when I was still running 2.0.7 (yesterday). The behavior I see when I try it manually is: [root@kepler:~]# /usr/local/sbin/smbd -D [root@kepler:~]# ps -aux | grep smbd root 92332 0.0 0.9 1036 528 p0 R+ 11:13AM 0:00.01 grep smbd [root@kepler:~]# kill -HUP `cat /var/run/smbd.pid` su: kill: (92040) - No such pid so the process is being started, and then just vanishes. I've tried running it with debug level set to 3 or 4, but nothing shows up in the log except smbd starting and loading some parameters. None of the Win98 computers on the subnet can see Can anyone offer any suggestions about what I can investigate next? I've never heard of behavior like this. -- Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message