[Samba] smbd and nmbd

Routledge, Carl Carl.Routledge at ucb-group.com
Thu Mar 14 07:00:20 GMT 2002


I started the daemons and they still didn't appear.
 
Mine version of Samba is a fairly old one 1.9 something and it was and
installp (AIX) file.
 
I did a find in the root directory (/) and searched for *.pid.
 
On my system it is /var/samba/locks.
 
Do you have to have a certain version of AIX to be able to use the latest
Samba??
 
Cheers
 
Carl



-----Original Message-----
From: Joel Hammer [ mailto:Joel at HammersHome.com
<mailto:Joel at HammersHome.com> ]
Sent: Thursday, March 14, 2002 14:33
To: Routledge, Carl; samba at lists.samba.org
Subject: Re: [Samba] smbd and nmbd


I don't think those lock files are around unless the daemons are running.
And, depending on how the daemons were compiled, they might be in several
locations.
Where have you looked?
Have you tried locate smbd.pid?
There is a /var/lock/samba directory on my system left over, I believe, from
my original distro specific installation of samba.
Joel

On Thu, Mar 14, 2002 at 03:08:14PM +0100, Routledge, Carl wrote:
>  Thanks for sending this replay, it looks like exactly what I need.  But I
> have little problem, I have got the smbd.pid and nmbd.pid files.  I looked
> in the lock directory and they aren't there.
>
>
>
> -----Original Message-----
> From: Joel Hammer [ mailto:Joel at HammersHome.com
<mailto:Joel at HammersHome.com> 
> < mailto:Joel at HammersHome.com <mailto:Joel at HammersHome.com> > ]
> Sent: Thursday, March 14, 2002 12:11
> To: Routledge, Carl; samba at lists.samba.org
> Subject: Re: [Samba] smbd and nmbd
>
>
> If I follow this, you had smbd and nmbd in your inetd.conf file.
> If so, the inetd was watching those ports.  This is not the suggested
> arrangement.
>
> It is easy to make a startup script for these two daemons. Here is the
> script that I use.
>
> #!/bin/bash
> case "$1" in
>  start)      
>   killall smbd
>   killall nmbd
> /usr/local/samba/bin/smbd -D
> /usr/local/samba/bin/nmbd -D
>   ;;
>
>  stop)
>   killall smbd
>   killall nmbd
>  ;;
>  reload)
>  kill -SIGHUP `cat /usr/local/samba/var/locks/smbd.pid`
>  kill -SIGHUP `cat /usr/local/samba/var/locks/nmbd.pid`
>  ;;
>  *)
>  echo Usage:
>  echo start stop reload
>  ;;
> esac
> exit 0
>
>
> There may already be a samba startup script around on your box.
>
> The location of your binaries and lock files might be different from mine.
I
> used the tarball from samba.org and accepted the defaults.
>
> If you don't want to mess around with leaning about run levels and all,
and
> just want a quick and dirty solution, put this script into your equivalent
> of rc.local. If you need help on figuring out how to make startup scripts
> start and stop daemons at various run levels, post again.
>
> Joel
>
>
>
> > I had a problem were smbd wouldn't start, it always give me an error
> message
> > in the log file.
> >
> > standard input is not a socket, assuming -D option
> > bind failed on port 139 socket_addr=0.0.0.0 (Address already in use)
> >
> > So I stopped the TCP Daemons and tried to start it and it worked.
> >
> > So I took both entry's out of the inetd.conf file (nmbd and smbd) and
> > restarted the server.  Obviously they didn't start automatically.
> >
> > But when I went to started them manually, they both worked fine.
> >
> > So my question is, is there any other way of automatically starting them
> at
> > start-up.
> >
> > Cheers
> >
> > Carl
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  http://lists.samba.org/mailman/listinfo/samba
<http://lists.samba.org/mailman/listinfo/samba> 
> < http://lists.samba.org/mailman/listinfo/samba
<http://lists.samba.org/mailman/listinfo/samba> >
>






More information about the samba mailing list