I would really suggest you use swat only for reading documentation easily and use vi to edit smb.conf and run the scripts manually. You'll never learn to troubleshoot things if you don't. Even for documentation, I find man smb.conf faster and easier to use than swat. Get out of the GUI habit as fast as you can. Now, for your problem. What does ps ax | grep mbd show? Find your startup scripts. I don't know where suse puts them, and start these things by hand. Here is all I need to get my daemons running. I suspect your script is more complicated, needlessly IMHO. Your paths may be different.
#!/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 Joel On Wed, Sep 25, 2002 at 04:00:05PM +1000, John Blue wrote: > I am using Suse V8 with KDE3 and running Samba 2.2.3a, and very much > feeling my way as I get into Linux. > > Using Swat I checked Status and it said smbd running, nmbd not > running. > > If I use KDE process table I can see nmbd as PID 714 and smbd as PID > 719. > > I cannot start or restart nmbd from Swat ? > > Any clues as to what the problem is here? > > John > > > > > This email has been pre-scanned using the latest Anti Virus > software for your peace of mind. > > Please remember to maintain your own anti virus up to date with > the latest reference files. > -- > To unsubscribe from this list go to the following URL and read the > instruction -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
