also sprach Michael Prokop m...@debian.org [2012.10.22.2229 +0200]:
I am not running a minion on the host the master runs on, currently.
Did you restart the salt process?
Yes, of course. The problem is not with the daemon. The problem is
that the salt CLI writes directly to the filesystem.
* martin f krafft [Mon Oct 15, 2012 at 12:53:34PM +0200]:
also sprach Ulrich Dangel u...@spamt.net [2012.10.15.1051 +0200]:
The problem is that salt-minion and the salt-master use the same
directory for different purpose. On startup the salt-minion as well as
the salt-master both check the
retitle 690481 Can't run salt-master and salt-minion as different users on the
same machine
forwarded 690481 https://github.com/saltstack/salt/issues/1488
thx
I do not quite understand why salt/salt-master are using the
filesystem for IPC instead of the sockets in /tmp/salt-unix, and
what
also sprach Ulrich Dangel u...@spamt.net [2012.10.15.1051 +0200]:
The problem is that salt-minion and the salt-master use the same
directory for different purpose. On startup the salt-minion as well as
the salt-master both check the specified directories and adjust the
permissions of these
Package: salt-master
Version: 0.10.1-3
Severity: normal
When run as non-root (salt.salt in my case), and after chown'ing
/var/cache/salt, I cannot execute remote commands. The reason is
that an invocation like
# salt '*' test.ping
creates e.g.
5 matches
Mail list logo
