similar to: root preexec

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 >

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, >> >>

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

I have a perl script that I'd like to use to create windows 9x login scripts at login time but I cannot get the process to work right. I have RedHat 7.3 (actually the k12ltsp v2.1.0 which is a modified RH7.3) set up as a domain controller which is working well. Manually created login scripts run fine on the workstations at login. I'm using a netlogon script I found at

I'm looking for a simple solution to log a single entry for each login to a Samba PDC. My current attempt(s) of using a root prexec script in either the [netlogon] share definition or the [global] section are working, but not exactly as expected. In [netlogon] I have an entry: root preexec = /path/to/script/makelogonscript.pl %g %u %m %I ...where makelogonscript.pl generates a

Running Samba 2.2.2, having troubles with preexec when it involves the path parameter: Log on to the samba server as kris, user "users". %U expands to kris, %G expands to users. [profile] path = /data/profile/%U preexec = /bin/mkdir -m 700 /data/profile/%U writable = yes create mode = 0600 directory mode = 0700 This fails to work, Samba reports that it could not

On Tue, 13 Jun 2017 10:33:43 +0200 Udo Willke via samba <samba at lists.samba.org> wrote: > Hello Rowland, > > Am 12.06.2017 um 19:32 schrieb Rowland Penny via samba: > > On Mon, 12 Jun 2017 10:04:56 -0700 > > Luke Barone via samba <samba at lists.samba.org> wrote: > > > >> Hi list, > >> > >> We have a script we are using to

Having received no responses, I will try again. I can't seem to get preexec to work as stated in my earlier email given below. Any help would be most appreciated. I am using samba-2.0.3-19990228 in combination with RH 5.2 with kernel-2.2.1. Thanks, Carey ---------- Forwarded message ---------- Date: Tue, 13 Apr 1999 11:35:03 -0500 (CDT) From: Carey F. Cox <carey@tabasco.lamar.edu>

Hello, I've been testing out 3.0.25 before putting it into production and came across an issue. As a simple example.. in a share definition root preexec = echo "hey there, hi there, hello" > /tmp/hiya.txt works fine under 3.0.24 not so under 3.0.25, /tmp/hiya.txt isn't created. Cranking up the debugging and using some other similiar tests it seems to me that Samba is in

Good Morning and thank you for your input. I had and still do understand what both preexec and root preexec do. I had also and still do understand the paths you had explained. I, however, had also already explained on 18 May 2015 15:31:55 CEST why your first solution was _not_ a viable option for us (server2 == NETAPP under warranty). I had also already explained on 21 May 2015 22:41:17 CEST

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

Msdfs proxy is pointing to another instance of samba servers, it passes through. I think running preexec there on the other instance will do the trick. Greetings Daniel EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet: www.tropenklinik.de

ok ok ... Names have been changed to protect the inoccent. This installation is being used to mitigate a server migration by providing read-only access to the new shares under the old server name. We have duplicated all the current shares on the new server (NETAPP) as {share name}_ro and created equivalent shares on the SAMBA installation as DFS proxies that point the client to that read-only

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

On Sun, 2016-10-30 at 14:10 +0100, Leander Schäfer via samba wrote: > Hi, > > I make use of shadow_copy2 and root preexec. The vfs root preexec is  > responsible to auto create home directories which initially don't > exist.  > The script behind it is well tested and works perfectly. > Unfortunaltely  > shadow_copy2 seems to be called before root preexec and fails due

Helo, I'm having a problem creating a share. When creating a user share, I use the preexec function to create their folder. Everything works fine. If I activate the shadowcopy 2 module, the preexec function no longer works for the share. The same applies to the root preexec function. To get around the problem, I use the preexec function at global level. I'd like to know whether this is

Hi, The Server to which the msdfs is pointing is a netapp. Though we theoretically can access the shell on it then begin to mess around there, we would really like to avoid that. Warranty and such make it a bit of a legal issue. That is the reason we went with a separate instance in the first place and now wonder why the preexec doesn't fire. There is nothing in tmp of the msdfs box. Like

hello, in first sorry for my poor english i use this script to test if a user is already connected. #!/bin/bash resultat=$(/usr/local/samba/bin/net status sessions |grep $1 | awk '{print$2}') if [ "X${resultat}" == X ]; then exit 0 else exit 1 fi in the smb.conf i add these lines : [home] root preexec = /usr/local/samba/bin/check-session %u root preexec close = yes

Hi, I make use of shadow_copy2 and root preexec. The vfs root preexec is responsible to auto create home directories which initially don't exist. The script behind it is well tested and works perfectly. Unfortunaltely shadow_copy2 seems to be called before root preexec and fails due to the missing ZFS home share which causes the session to fail completely before root preexec even has a

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