On Thu, May 20, 2010 at 03:50:20PM -0700, Craig White wrote:
not until you run the command as suggested much earlier...
/usr/sbin/smbd -iF
which will launch it iteractively and output everything to standard out
- the console itself and then let us know what it says.
Hi Craig,
On Thu, May 20, 2010 at 06:49:33PM -0400, Kwan Lowe wrote:
The service scripts can check for lock files. Do you have any stale
locks in /var/run/subsys?
Thanks Kwan.
If I remove /var/run/smbd.pid (and /var/run/nmbd.pid for that matter), the
init.d/smb file still fails to get smbd running
On Thu, May 20, 2010 at 04:40:26PM -0700, Craig White wrote:
sounds like a hardware issue - have you run memtest86 on this computer?
No, haven't. My experience with hardware issues is that they rarely
introduce 100% repeatable software errors. This one is entirely consistent
in its behavior,
On Thu, May 20, 2010 at 04:44:20PM -0700, Craig White wrote:
I should have added that there should be a core dump in
/var/log/samba/cores/smbd which if you could analyze, would give you some
hints
As you might expect at this point, that's a totally empty directory. The
lack of a core dump
On Thu, May 20, 2010 at 07:58:19PM -0400, Ryan Manikowski wrote:
Tell them to join the debian-users list and see what kind of intelligent
discussion goes on there. They will be back to Centos in a week. =)
Too true!
Whit
___
CentOS mailing list
On Thu, May 20, 2010 at 04:55:29PM -0700, Jerry Franz wrote:
I would start by comparing the values of all the environment variables
between running as /bin/sh and /bin/bash:
env bash_env.txt
/bin/sh
env sh_env.txt
exit
diff bash_env.txt sh_env.txt
Jerry,
That's a good idea. To
On Thu, May 20, 2010 at 06:17:10PM -0700, Benjamin Franz wrote:
Have you looked in /var/log/messages for errors from smbd? I don't
remember seeing that anywhere in your T/S list.
Yup. I've grepped all the logs. Nothing from smbd at all. I also enabled
kern and daemon logs, just in case those
101 - 107 of 107 matches
Mail list logo
