search for: pkg_rundir

...to /tmp are blocked by SELinux policy (https://bugzilla.redhat.com/show_bug.cgi?id=424091). From the SELinux's point of view it is bad when system services try to write into /tmp (for detail see http://danwalsh.livejournal.com/11467.html). The solution looks simple - just to switch from /tmp to PKG_RUNDIR (line 472 in deliver.c for dovecot 1.0) for writing the temp files. But this raises two questions - will it really work and when yes, is it acceptable for the author? Thanks, Dan -- Fedora and Red Hat package maintainer

.../lib/dovecot) is hard-coded as the location of things like the ssl-parameters.dat file and the replicator database. Replace all these uses of PKG_STATEDIR with a state_dir setting which defaults to PKG_STATEDIR but can be overridden in dovecot.conf, in the same way base_dir can be used to override PKG_RUNDIR. Signed-off-by: <chris at arachsys.com> --- src/config/Makefile.am | 1 - src/doveadm/doveadm-instance.c | 10 ++++------ src/doveadm/doveadm-mount.c | 3 +-- src/doveadm/doveadm-settings.c | 2 -- src...

...uthentication. The socket is now created in /var/spool/postfix/private/auth. authtest do not catch up the change. Reading source I?ve seen that path to auth sockets is written explicitly in function authtest_passdb in util/authtest.c to: if (auth_socket_path == NULL) auth_socket_path = PKG_RUNDIR"/auth-client?; I know I can launch authtest specifing path to socket, but I think it would be better if authtest would parse dovecot.conf and find out where sockets are. I?ve tried to code it by myself, but I?ve had no time to go deep in the code. Is it possible to have this ?feature? added??...

...(SET_STR, instance_name), DEF(SET_STR, log_path), DEF(SET_STR, info_log_path), DEF(SET_STR, debug_log_path), @@ -52,6 +53,7 @@ static const struct setting_define master_service_setting_defines[] = { static const struct master_service_settings master_service_default_settings = { .base_dir = PKG_RUNDIR, .state_dir = PKG_STATEDIR, + .instance_name = PACKAGE, .log_path = "syslog", .info_log_path = "", .debug_log_path = "", diff --git a/src/lib-master/master-service-settings.h b/src/lib-master/master-service-settings.h index e5b5ace..d7f1a80 100644 --- a/src/lib...

...e ENV_SYSTEMD "" 10.20 +#endif 10.21 +#ifdef DEBUG 10.22 +# define ENV_GDB " GDB" 10.23 +#else 10.24 +# define ENV_GDB "" 10.25 +#endif 10.26 +/* </settings checks> */ 10.27 + 10.28 static const struct master_settings master_default_settings = { 10.29 .base_dir = PKG_RUNDIR, 10.30 .libexec_dir = PKG_LIBEXECDIR, 10.31 + .import_environment = "TZ" ENV_SYSTEMD ENV_GDB, If I am not missing anything, then there seems to be a problem with kerberos sasl with ldap lookups. Thank you, Trever Adams Reference: http://hg.dovecot.org/dovecot-2.0/rev/cec7fa92ff48 Refe...

Hello, When running multiple instances of dovecot on the same host (or running multiple docker container), it is hard to distinguish logs from different processes: the syslog entries are all prefixed with the same identifier "dovecot" It is hardcoded here: https://github.com/dovecot/core/blob/master/src/lib-master/master-service.c#L420 Would it make sense to use the already implemented