Actually, there is another solution: SWAT manages permissions using PAM,
and using rights on /etc/samba/smb.conf.
So the solution is just to allow you user(s) to write to
/etc/samba/smb.conf.
Example:
adduser myuser adm
chgrp adm /etc/samba/smb.conf
chmod g+w /etc/samba/smb.conf
Hope it helps
Currently SWAT avoids requiring config file entries (or the passdb
database), as it rewrites them (and it doesn't want bootstrap concerns).
Fair enough, but how is the administrator of a Debian system
configured to use only sudo for root access supposed to log in? (Hmm,
what does Ubunto do?)
On Sun, 2006-07-16 at 15:31 +0200, Christian Pernegger wrote:
Package: swat
Version: 3.0.22-1
Severity: important
debian-installer now offers the option to disable the root account and
grant a normal user full sudo priviledges instead.
With such a setup swat is not usable, since it
Package: swat
Version: 3.0.22-1
Severity: important
debian-installer now offers the option to disable the root account and
grant a normal user full sudo priviledges instead.
With such a setup swat is not usable, since it seems to insist on a
login with username 'root' + root's unix password.
4 matches
Mail list logo
