Al,
Never used swat, but on Suse, use:
#rcnmb stop
#rcsmb stop
to kill the processes. Then just start them manually and check to logs.
#rcnmb start
#rcsmb start
Suse has split the scripts that start smbd and nmbd so it is possible swat
is having problems. I have samba 3.07 running fine on Suse 9.0 and Mdk 7.2.
Another possibility is that one of the processes has died and has left a
lock file or PID file around that is giving you problems. After stopping the
daemons, check for leftover lock of PID files and nuke them if found and try
restarting.
(These are just stabs from past posts I have read)
--
David C. Rankin, J.D., P.E.
Rankin * Bertin, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankin-bertin.com
--
----- Original Message -----
From: <Forum.Mail@GMX.Net>
To: <samba@lists.samba.org>
Sent: Tuesday, November 30, 2004 4:22 PM
Subject: [Samba] smbd won't start - new installation
> Hi all,
>
> I installed SuSe 9.1 with Samba 3.0.4-suse. I can not get the smbd to
> start from swat, but nmbd is running, When I start smdb and nmbd with
> the SWAT restat then ps -A shows that the processes are there and it
> seems to run, but not according to the 'status' of swat. Copying
files
> from samba and printing with the shared printers work though. The
> printers show "access denied, no connection" in the W$ print
status.
>
> Is it a bug or do I miss some configuration with localhost:901 and SWAT?
>
> --
> Greetings,
>
> :-)
>
> Al Active
> _______________________________________________
> " Experience: the most brutal of teachers
> but you learn, my God, you learn "
>
> - C S Lewis -
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>