Displaying 5 results from an estimated 5 matches for "tigchelaar".
2001 Dec 12
3
Problems with a dying winbindd daemon
Hello there!
Since i am new to this list i will introduce myself in short: My name is
Martijn Olivier Tigchelaar (Martijn). I am from the Kingdom of The
Netherlands and i live in Eindhoven which is the hometown of Philips. To
earn my living i do a lot of things - sitting behind my computer is just one
of those.
Currently i am having problems with the Winbindd daemon - it seems to die
silently... Here is what...
2010 Mar 07
3
Can PXElinux be used to dynamically pass DHCP option 252 to a PXE client?
...delay that a network sniffer will show the requests go to the TFTP server at port 4011...
So hmm - Can this be done? Can PXElinux be used to dynamically pass DHCP option 252 to a PXE client based on for example menu choices?
Looking forward to responses. Thanks in advance!
Sincerely,
Matijn Tigchelaar.
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop
2001 Dec 15
3
winbindd: local unix users vs. NTdomain users ........
Hi!
I use Samba 2.2.2 on Linux Red Hat 7.1.
My Samba server is NT domain member (security = domain),
and I use winbindd.
I detect some strange situation, as I look. See below.
For example, my NT domain is MYDOMAIN (PDC implemented
on NT4), and this domain have user myuser (MYDOMAIN+myuser
as see him Samba&Winbindd).
Linux, which run Samba&winbindd, have local user myuser too.
Local
1997 Aug 08
12
Logon scripts
I am having difficulty getting my logon scripts to started when I logon. My
clients are Windows95, server is RedHat Linux 4.2, Samba 1.9.17alpha5.
This is my smb.conf file:
; *******************************************************************
; *
; * Samba config file for
; * Quinn P. Coldiron
; *
; *******************************************************************
;
2002 Mar 12
6
Memory leak in winbindd
I'm running Samba 2.2.3a on NetBSD. I've been having an annoying
problem with winbindd dying inexplicably. I finally found a test that
seems to (eventually) kill it:
while wbinfo -t > /dev/null; do /usr/bin/true; done
The problem is a memory leak in winbindd. Actually, wbinfo -t will
still work, but wbinfo -u doesn't (response.extra_data is always null).
Is this a known