Bug#337070: winbind: same malfunction here

2005-11-06 Thread Steve Langasek
On Sun, Nov 06, 2005 at 09:17:21AM +0100, Christian Perrier wrote: > > How about adding this to the init script then?: > > if [ "`testparm -s --parameter-name='domain logons' 2>/dev/null`" = "No" ] \ > >&& [ "`testparm -s --parameter-name='security' 2>/dev/null`" != "DOMAIN" > > ] > > then >

Bug#337070: winbind: same malfunction here

2005-11-06 Thread Christian Perrier
> How about adding this to the init script then?: > > if [ "`testparm -s --parameter-name='domain logons' 2>/dev/null`" = "No" ] \ >&& [ "`testparm -s --parameter-name='security' 2>/dev/null`" != "DOMAIN" ] > then > exit 0 > fi I'm not completely sure that using winbindd is limited to

Bug#337070: winbind: same malfunction here

2005-11-06 Thread Steve Langasek
On Sun, Nov 06, 2005 at 08:20:31AM +0100, Christian Perrier wrote: > > So does this mean that winbindd can't be started on systems that are members > > of workgroups, rather than domains? Should we be splitting libnss_wins into > My knowledge of winbind would answer "yes" to the above question.

Bug#337070: winbind: same malfunction here

2005-11-05 Thread Christian Perrier
> So does this mean that winbindd can't be started on systems that are members > of workgroups, rather than domains? Should we be splitting libnss_wins into My knowledge of winbind would answer "yes" to the above question. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsu

Bug#337070: winbind: same malfunction here

2005-11-05 Thread Steve Langasek
On Sun, Nov 06, 2005 at 08:59:12AM +1100, Andrew Bartlett wrote: > On Sat, 2005-11-05 at 21:55 +0100, Axel Ludszuweit wrote: > > Package: winbind > > Version: 3.0.20b-2 > > Followup-For: Bug #337070 > > Before upgrading winbind works fine, the smb.conf is left unchanged. I > > use winbind only for

Bug#337070: winbind: same malfunction here

2005-11-05 Thread Andrew Bartlett
On Sat, 2005-11-05 at 21:55 +0100, Axel Ludszuweit wrote: > Package: winbind > Version: 3.0.20b-2 > Followup-For: Bug #337070 > > Before upgrading winbind works fine, the smb.conf is left unchanged. I > use winbind only for host name resolution in a little network of three > Windows and on Debian

Bug#337070: winbind: same malfunction here

2005-11-05 Thread Axel Ludszuweit
Package: winbind Version: 3.0.20b-2 Followup-For: Bug #337070 After upgrading from winbind (3.0.14a-6) to 3.0.20b-2 and samba (3.0.14a-6) to 3.0.20b-2 I have the same behaviour. Additonally here the contents of the /var/log/samba/log.winbind file: [2005/11/05 21:14:34, 1] nsswitch/winbindd.c:ma