similar to: Can't get 'root preexec' to run

Displaying 20 results from an estimated 10000 matches similar to: "Can't get 'root preexec' to run"

2015 Oct 20
5
Can't get 'root preexec' to run
Looks like my nfsv4 kerberos and root access problem. In that case, root didnt have a kerberos ticket, and was not allowed to access the needed folder. I think this is a bit the same. Creating the users and profiles shares from ADUC is working fine for me but not scripted from user root. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at
2015 Oct 21
2
Can't get 'root preexec' to run
Hi Rowland, thank you for your effort! However, this is entirely not what I am trying to achieve. What I am trying to achieve is to get the "prexec" method to work. The reason behind this is that I would like to have a zfs data set created per user in an automatic (scripted) way. The reason behind that is that if I do this by hand - from a domain admin account and with the ACL
2015 Oct 15
1
Can't seem to get 'root preexec' to run
Hi, I am trying to automatically create nested zfs data sets as home directories. I have a script that works fine if I execute it manually as root (auth via public key). It also creates a short log file in the same dir. However, this section in my smb.conf (on the DC) doesn't seem to execute (no data set created, no log file) on user logon (on a member server): [homes] comment =
2015 Oct 21
3
Can't get 'root preexec' to run
Rowland, I apologize: I have overlooked this answer of yours before my last post. >> I think you may still be missing the obvious, I was suspecting that. >> '[homes]' *does not work* on a DC. You mean in general or in my assumed use case? Am 21.10.2015 um 11:27 schrieb Rowland Penny: > On 21/10/15 10:07, Ole Traupe wrote: >> Hi Rowland, >> >>
2015 Oct 21
1
Can't get 'root preexec' to run
Maybe I finally figured it out. I found that sentence "For example, the [test] and [homes] sections are unique disk shares; they contain options that map to specific directories on the Samba server." here: https://www.samba.org/samba/docs/using_samba/ch06.html Does that mean that this "preexec" in the [homes] section is not invoked if the user is accessing his or her home
2015 Oct 21
1
Can't get 'root preexec' to run
On 21/10/15 13:30, Rowland Penny wrote: > On 21/10/15 12:41, mourik jan heupink wrote: >> Hi, >> >> On 10/21/2015 01:21 PM, Rowland Penny wrote: >>> I am now beginning to think it doesn't work at all, if samba4 is >>> involved in any way. I knew that it wouldn't work on a DC (probably >>> because the user is DOMAIN\username and not just
2015 Oct 20
0
Can't get 'root preexec' to run
You tried the pam module mkhomedir ? And have your tried : root preexec = "/usr/local/samba/scripts/createzfshome.sh %U" or root preexec = /usr/local/samba/scripts/createzfshome.sh "%U" Is the homedir on a NFS mounted dir? Exports correctly set? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Ole
2015 Oct 21
0
Can't get 'root preexec' to run
Louis, thanks for the idea! I can execute the script as root on linux (tested this), because I do folder (zfs data set) creation via remote ssh commands, so not in the domain context. But the point is that the script won't even execute. Even on failure, there would be a log file created by my script which can't be found anywhere. Ole Am 20.10.2015 um 17:29 schrieb L.P.H. van
2015 Oct 21
0
Can't get 'root preexec' to run
On 21/10/15 10:07, Ole Traupe wrote: > Hi Rowland, > > thank you for your effort! However, this is entirely not what I am > trying to achieve. > > What I am trying to achieve is to get the "prexec" method to work. > > The reason behind this is that I would like to have a zfs data set > created per user in an automatic (scripted) way. The reason behind >
2015 Oct 21
4
Can't get 'root preexec' to run
Hi, On 10/21/2015 01:21 PM, Rowland Penny wrote: > I am now beginning to think it doesn't work at all, if samba4 is > involved in any way. I knew that it wouldn't work on a DC (probably > because the user is DOMAIN\username and not just username), but from my > experiment (see my earlier post) it doesn't seem to work at all, try > your setup with '[home]' and a
2015 Oct 21
4
Can't get 'root preexec' to run
Oh, and of course the auto-creation works if you put the path \\server\home\user into the "Profiles" tab of the user properties in the ADUC console. This is explicitly, what the samba wiki suggests, as it is directed to using Windows clients. As soon as you press "Ok", the folder is created Am 21.10.2015 um 14:52 schrieb Rowland Penny: > On 21/10/15 13:32, Ole Traupe
2015 Oct 21
2
Can't get 'root preexec' to run
Hi Ole, On 10/21/2015 02:38 PM, Ole Traupe wrote: > MJ, thanks a lot! Just to make sure I get you right: > > This section is in the smb.conf. > a) on the DC acting as file sever as well, or > b) on a separate file server running Samba 4.1.17? on a separate fileserver. DC's are 4.2.4, fileserver 4.1.17. > The user log-on happens on a third machine, that is neither DC nor
2015 Oct 22
3
Can't get 'root preexec' to run
The next interesting question for me is: If I put '\\server\%username%' into ADUC Windows part (or \\server\username explicitly, for that matter), Samba on 'Ok/Apply' registers the attempt to access a non-existing share and applies the [homes] section (executes 'root preexec'). I tested that. However, the user doing this is the domain admin. So Samba would look that
2015 Oct 20
2
getent passwd not showing domain users at boot
Mark, As you try to extract all users from AD and as it is not always advisable I would try into your rc script to retrieve only one user at boot time, just to check if winbind is not working at all at that moment or if it refuse to extract all domain users at that moment... Cheers, mathias 2015-10-20 10:18 GMT+02:00 Ole Traupe <ole.traupe at tu-berlin.de>: > Mark, did you make sure
2015 Oct 21
3
Can't get 'root preexec' to run
Rowland, thanks for your effort, I highly appreciate it! From what I had read before... [home] would be an arbitrarily named share and its preexec command would execute whenever a domain user connects to it [homes] is a special purpose section in the smb.conf that comes into play whenever a domain user connects to his or her home dir defined on the DC What MJ is telling seems to confirm
2015 Oct 21
5
Can't get 'root preexec' to run
On a Windows domain member client in the ADUC console, you specifiy the home dir path that is to be used on Windows machines on the "Profile" tab. As soon as you click 'Ok' (or 'Apply' for that matter), the folder is created (by the DC via your domain admin account) on the Samba server hosting the share the path you provided leads to. Try it, its nice an simple.
2015 Oct 21
2
Can't get 'root preexec' to run
On 21/10/15 17:37, Ole Traupe wrote: > I think I finally managed to understand the [homes] part of the man > pages, and what my problem is: > https://www.samba.org/samba/docs/man/manpages/smb.conf.5.html > > The misunderstanding comes from my practice I learned on Windows to > just share the "\\server\home" directory and to create per-user > sub-folders
2015 Oct 21
2
Can't get 'root preexec' to run
On 21/10/15 18:19, Ole Traupe wrote: > Well, I do. That is not the problem. > > The problem was that I wasn't used to have user homes to be shares > themselves. And when I share \\server\home and want to have the folder > \\server\home\newuser to be auto-created, but I actually connect to > the share [home] (\\server\home), this section in the smb.conf is > always
2015 Oct 22
2
Can't get 'root preexec' to run
On 22/10/15 10:37, Ole Traupe wrote: > Rowland, what are [homes] shares on a Unix machine? It is described in the smb.conf manpage, but briefly if you try to connect to a share called 'username' and samba knows nothing about a share called 'username' it checks if there is a user called 'username'. If this user exists, it obtains the users Unix homedir and uses this
2015 Oct 21
1
getent passwd not showing domain users at boot
I added `service winbind status` to the beginning of my rc.local script and, after booting, saw the message: "winbind stop/waiting". So you're right, winbind is not running. Hmmm, I thought rc.local was the last thing to run at boot time. winbindd is run as a daemon, so I suppose rc.local could run before winbind has a chance to get all its ducks in a row. I'll try looping in