search for: 403600

...0:00 /usr/sbin/smbd -D root 2684 0.0 0.0 296524 4516 ? S Aug29 0:00 /usr/sbin/smbd -D root 2730 0.0 0.0 265088 9696 ? S Aug29 0:00 /usr/sbin/winbindd root 2745 0.0 0.0 265220 9560 ? S Aug29 0:00 /usr/sbin/winbindd root 2746 0.0 0.1 403600 16412 ? S Aug29 0:01 /usr/sbin/winbindd So, from that, can I ask these questions: Why isn't 'smbd' running ? Is 'nmbd' running ? Why aren't you running 'winbind' as a daemon ? Why do feel you don't need a process group for winbind ? Rowland

Hi, On Wed, Mar 07, 2001 at 10:05:07AM +1100, Damien Miller wrote: > > now to patching openssh to actually *use* prngd/socket... :-) > Was done last week - use the "--with-prngd-port=XXX" configure option. OpenSSH + PRNGD + SCO3 seem to work nicely. Thanks! One other thing: I'm not fully convinced that current OpenSSH does everything right regarding utmp/wtmp on SCO3

...2684 0.0 0.0 296524 4516 ? S Aug29 0:00 > /usr/sbin/smbd -D > root 2730 0.0 0.0 265088 9696 ? S Aug29 0:00 > /usr/sbin/winbindd > root 2745 0.0 0.0 265220 9560 ? S Aug29 0:00 > /usr/sbin/winbindd > root 2746 0.0 0.1 403600 16412 ? S Aug29 0:01 > /usr/sbin/winbindd > > So, from that, can I ask these questions: > > Why isn't 'smbd' running ? > I didn't set this up, but I assume the sysadmins didn't run it because they, like Luca, probably assumed that smbd was for serv...

El 2/9/18 a les 10:39, Rowland Penny via samba ha escrit: > All of this is just a sticking plaster on the problem, if winbind is > crashing on a regular basis, we need to know this and will need > level 10 logs, debug info etc. Without this info, it will never get > fixed. Meanwhile, I need my server to keep running, so the plaster looks fine. Besides, winbind isn't crashing,