On 12/08/15 15:44, sandy.napoles at eccmg.cupet.cu wrote:> OK, there could be several things going wrong here: > Do you have /usr/local/samba/bin and /usr/local/samba/sbin at the start of your PATH ? > -----> Yes I have both, in /usr/local/samba there's a folder bin and sbinEr, no, if you open a terminal, type 'env', then amongst the output there will be a line that starts with 'PATH'. This is the order in which to check for an executable, it need to start like this: PATH=/usr/local/samba/sbin:/usr/local/samba/bin:~~~~~ and so on. To change it, type 'export PATH=/usr/local/samba/sbin:/usr/local/samba/bin:$PATH' This will set it for the current session, your homework is to find out how to set it permanently :-D Rowland> > You have (in smb.conf) > workgroup = domain > realm = domain.cu > > -----> sorry, the correct way is > workgroup = ECCMG > realm = ECCMG.CUPET.CU > path = /usr/local/samba/var/locks/sysvol/eccmg.cupet.cu/scripts > > Can you helpme, please. >
Am 12.08.2015 um 16:48 schrieb Rowland Penny:> On 12/08/15 15:44, sandy.napoles at eccmg.cupet.cu wrote: >> OK, there could be several things going wrong here: >> Do you have /usr/local/samba/bin and /usr/local/samba/sbin at the >> start of your PATH ? >> -----> Yes I have both, in /usr/local/samba there's a folder bin and sbin > > Er, no, if you open a terminal, type 'env', then amongst the output > there will be a line that starts with 'PATH'. This is the order in which > to check for an executable, it need to start like this: > > PATH=/usr/local/samba/sbin:/usr/local/samba/bin:~~~~~ and so on. > To change it, type 'export > PATH=/usr/local/samba/sbin:/usr/local/samba/bin:$PATH' > > This will set it for the current session, your homework is to find out > how to set it permanently :-Din case of a sysvinit script there export PATH=........ in case of a systemd-unit Environment="PATH=" and in case he is using systemd /usr/local is most likely *not* in PATH because systemd cleans up environment vars by default for good reasons -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <lists.samba.org/pipermail/samba/attachments/20150812/6b927162/signature.sig>
On 12/08/15 15:54, Reindl Harald wrote:> > Am 12.08.2015 um 16:48 schrieb Rowland Penny: >> On 12/08/15 15:44, sandy.napoles at eccmg.cupet.cu wrote: >>> OK, there could be several things going wrong here: >>> Do you have /usr/local/samba/bin and /usr/local/samba/sbin at the >>> start of your PATH ? >>> -----> Yes I have both, in /usr/local/samba there's a folder bin and >>> sbin >> >> Er, no, if you open a terminal, type 'env', then amongst the output >> there will be a line that starts with 'PATH'. This is the order in which >> to check for an executable, it need to start like this: >> >> PATH=/usr/local/samba/sbin:/usr/local/samba/bin:~~~~~ and so on. >> To change it, type 'export >> PATH=/usr/local/samba/sbin:/usr/local/samba/bin:$PATH' >> >> This will set it for the current session, your homework is to find out >> how to set it permanently :-D > > in case of a sysvinit script there > export PATH=........ > > in case of a systemd-unit > Environment="PATH=" > > and in case he is using systemd /usr/local is most likely *not* in > PATH because systemd cleans up environment vars by default for good > reasons > > >Yet another reason not to use systemd, what has something that claims to be an init system to do with a users PATH ?? Rowland