Oh, note for the "does not crash the system", there is one other
modification that is required to be made at the same time: I need to
remove winbind from the pam.d/* files. In order for the system to
boot successfully when winbind is badly broken/crashed, I must
simultaneously remove it from nsswi
It doesn't crash the system, but it doesn't authenticate against
winbind, and winbind is still very broke (large quantity of log
messages, wbinfo -u don't return, etc).
--Jim
On Tue, May 18, 2010 at 12:07 PM, Chris Smith wrote:
> On Thu, May 13, 2010 at 1:12 PM, Jim Kusznir wrote:
>> Any more s
On Tue, May 18, 2010 at 3:19 PM, Eliel wrote:
> it would problably not crashs, but will not use winbind to authenticate
"Probably" doesn't answer the question. Yes, it wouldn't use winbind
to authenticate but the winbindd daemon would still be running and
maybe that additional info (whether it cr
On Thu, May 13, 2010 at 1:12 PM, Jim Kusznir wrote:
> Any more suggestions? Anyone actually using winbind successfully?
What changes if you change:
/etc/nsswitch.conf
-
passwd: compat winbind
group: compat winbind
to:
-
passwd: compat
group:
Ack, this message got burried in my mail reader...Thanks for the reply.
My entire smb.conf is included in my origional message to the list;
I'll paste it again here:
smb.conf
[global]
security = ads
netbios name = casas-lin
realm = CASAS.WSU.EDU
workgroup
Am I the only one experiencing such breaking from winbind? I'm
suspicious of whether it actually works at all, and if I can't get it
working better "real soon now", I'm going to have to ditch it all
together. I really can't afford half of my cpu resources tied up in
logging messages, or my critic
Some more info:
On my (working) Ubuntu 9.04 system, its often consistently at around
50% load, with winbind and syslogd using up that CPU. In
/var/log/syslog, I get fairly continuous logging of:
May 11 09:06:39 casas-thin-serv winbindd[11370]: rpc_api_pipe: host
ad1.casas.wsu.edu, pipe \NETLOG
Le 10/05/2010 19:14, Jim Kusznir a écrit :
Hi all:
I've got a couple Ubuntu 9.10 machines that are suffering from a
recurring failure of winbind that essentially crash the machine. When
the system is in the "crashed state", one can ping the system, but all
forms of login fail.
It's normal, winb
Hi all:
I've got a couple Ubuntu 9.10 machines that are suffering from a
recurring failure of winbind that essentially crash the machine. When
the system is in the "crashed state", one can ping the system, but all
forms of login fail. It will not even respond to tftpd requests; ssh
connections "
