Can anyone advise what to look for when the use of a root preexec statement kills a domain controller login process? I have samba 2.2.6 set up as a domain controller. It works every time with a manually created netlogon .bat file to map user drives. When I use a root preexec statement to automate script creation with a perl script I get a no domain login server available error. The perl script I'm using is one freely available on the web and it works perfectly when run from the command line. I've set log level to 5 and found that with the preexec in place there isn't even any log messages for the machine used to attempt login. I don't see any errors in the server logs - it just doesn't work.
Just for kicks I tried the little root preexec statement in the smb.conf man page that echo's a little blurb to /tmp/log and have found that I get the same results with that. It kills the domain logons.
I out of places to look in solving this - can anyone suggest any?
Just for kicks I tried the little root preexec statement in the smb.conf man page that echo's a little blurb to /tmp/log and have found that I get the same results with that. It kills the domain logons.
I out of places to look in solving this - can anyone suggest any?