rowlandpenny241155 at gmail.com
Wed Aug 12 15:07:22 UTC 2015
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
>> 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
>> 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
> 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
Yet another reason not to use systemd, what has something that claims to
be an init system to do with a users PATH ??
More information about the samba