On Fri, Oct 24, 2003 at 09:02:33AM -0700, Sagara Wijetunga wrote: > > Brian said it was necessary. I've checked a couple > > of our standard installs (which don't mess with the > > socket) and it's owned by root:root with rwx access > > for ugo. > > How I did that is by inserting chown statements after > authdaemond start line in /etc/init.d/sqwebmail: > /usr/local/share/sqwebmail/libexec/authlib/authdaemond > start > chown mailuser:mailgroup > /usr/local/share/sqwebmail/var/authdaemon/pid > chown mailuser:mailgroup > /usr/local/share/sqwebmail/var/authdaemon/socket
Oh I forgot about that. You can run authdaemond *as* the same user, with su: su vmail -c "/path/to/authlib/authdaemond start" (assuming that the authentication module(s) you want don't need root, e.g. they are not using the shadow password file; it's fine for LDAP and should be fine for other database backends) In this case you don't need to chown the socket, but you do need to chown the directory which it is created within. Regards, Brian.
