Displaying 5 results from an estimated 5 matches for "master_service_init_log".
2015 Mar 11
0
rawlog with -i not worked
...7 +390,7 @@
argv += optind;
if (argc < 1)
- i_fatal("Usage: rawlog [-f in|out] [-i] [-b] [-t]
<binary> <arguments>");
+ i_fatal("Usage: rawlog [-f in|out] [-a] [-b] [-t]
<binary> <arguments>");
master_service_init_log(master_service, "rawlog: ");
master_service_init_finish(master_service);
Am 09.03.2015 um 18:53 schrieb Hardy Flor:
>
> Without -i everything is wonderful, a coredump is with the -i
> parameter created
>
2010 Aug 30
1
[DC2.x ]pop3-login seg faults when compiled with gcc 4.5.2 and gold
Hello,
On FreeBSD, Dovecot 2.0.1 compiles fine with gcc45 and the other
services have no problem, but even without any optimizations (CFLAGS) at
all, pop3-login seg faults when a user tries to connect to Dovecot using
POP3.
As this is not the only application that has a problem with the latest
version of gcc (mod_php), there may be nothing that can be done on the
Dovecot side, but I thought I
2015 Mar 09
4
rawlog with -i not worked
Hello,
I have the rawlog enabled according to the
manual:http://wiki2.dovecot.org/Debugging/Rawlog
Without -i everything is wonderful, a coredump is with the -i parameter
created
****************************************
service imap-postlogin {
executable = script-login -d rawlog -i
user = vmail
}
****************************************
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012
2018 May 30
0
use instance-name for syslog?
..._name;
const char *log_path;
const char *info_log_path;
const char *debug_log_path;
diff --git a/src/lib-master/master-service.c b/src/lib-master/master-service.c
index 65b2753..d3e5281 100644
--- a/src/lib-master/master-service.c
+++ b/src/lib-master/master-service.c
@@ -297,7 +297,8 @@ void master_service_init_log(struct master_service *service,
if (!syslog_facility_find(service->set->syslog_facility,
&facility))
facility = LOG_MAIL;
- i_set_failure_syslog("dovecot", LOG_NDELAY, facility);
+ i_set_failure_syslog(service->set->instance_name, LOG_NDELAY,
+...
2018 May 30
3
use instance-name for syslog?
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