vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| This is my ~ 10th setting of virtual mail server based on: http://www.gentoo.org/doc/en/virt-mail-howto.xml I am trying to start saslauthd but it doesn't start or at least doesn't start the right way - I get the "saslauthd -v" output and it doesn't want to stop [!!] according to /etc/init.d/saslauthd it is supposed to have for pid but it is not created. I created it myself, nothing happend. I reemerged saslauth. it removed /var/lib/sasl2 and didn'tcreate a new one even though during emerge it checks if it is supposed to create one. maybe I should change something in the /etc/conf.d/saslauth? so that it accepts /usr/lib/sasl2/smtpd.conf pwcheck_method: saslauthd mech_list: LOGIN PLAIN instead of: pwcheck_method Any hints? How to stop such daemon? I am starting to be a bit nervous about that so called stable Gentoo. I am a gentoo user for almost a year and never had such problems with it. Now I'm trying to set up a SElinux but I encounter too many problems NOT-SElinux related (at least I think they have nothing to do with it - correct me if I'm wrong). The autoconf shouldn't be marked stable if it is the cause of emerge errors of squid, libwww and so on. Who the hell and on what basis marks such importatnt files stable? |
| Thread Tools | |
| Display Modes | |
|
|