[krbdev.mit.edu #3277] doubled kerberos logging to stderr

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[krbdev.mit.edu #3277] doubled kerberos logging to stderr

Greg Hudson via RT
My krb5.conf:

[logging]
? ? default = STDERR

...

When I start "krb5kdc -n" ?from the shell, I am getting:

2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): setting up network...
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): setting up network...
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): listening on fd 7: udp 172.17.2.38.750
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): listening on fd 7: udp 172.17.2.38.750
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): listening on fd 8: udp 172.17.2.38.88
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): listening on fd 8: udp 172.17.2.38.88
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): set up 2 sockets
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): set up 2 sockets
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): commencing operation
2005-12-06 16:04:06 Dec 06 16:04:06 firebird krb5kdc[21670](info): commencing operation

Looks like krb5-1.4.3/src/lib/kadm5/logger.c:klog_vsyslog(...) routine, which
formats these messages, outputs them twice.

Next, when I run exactly the same command, "krb5kdc -n", under daemontools,
it gets unhappy:

2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error
2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error

Replacing "default = STDERR" with "default = FILE:/proc/self/fd/2"
helps.

Fragment of strace output where it happens:

access("/etc/krb5.conf", R_OK) ? ? ? ? ?= 0
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
open("/dev/urandom", O_RDONLY) ? ? ? ? ?= 3
fstat64(3, {st_mode=S_IFCHR|0444, st_rdev=makedev(1, 9), ...}) = 0
read(3, "%\331\304\317@:\372\\\257\317\203\222u\22\341\3\237\4\340"..., 20) = 20
close(3) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 0
getpid() ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 2855
gettimeofday({1133726936, 181336}, NULL) = 0
getpid() ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 2855
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
time(NULL) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?= 1133726936
fcntl64(2, F_GETFL) ? ? ? ? ? ? ? ? ? ? = 0x1 (flags O_WRONLY)
write(2, "krb5kdc: cannot parse <STDERR>\n", 31) = 31
write(2, "krb5kdc: warning - logging entry"..., 46) = 46
fcntl64(2, F_GETFL) ? ? ? ? ? ? ? ? ? ? = 0x1 (flags O_WRONLY)
write(2, "krb5kdc: cannot parse <STDERR>\n", 31) = 31
write(2, "krb5kdc: warning - logging entry"..., 46) = 46

Looks like something fails here:

krb5-1.4.3/src/lib/kadm5/logger.c
...
? ? ? ? ? ? ? ? else if (!strcasecmp(cp, "STDERR")) {
? ? ? ? ? ? ? ? ? ? log_control.log_entries[i].lfu_filep =
? ? ? ? ? ? ? ? ? ? ? ? fdopen(fileno(stderr), "a+");
? ? ? ? ? ? ? ? ? ? if (log_control.log_entries[i].lfu_filep) {
is not set somehow ===> log_control.log_entries[i].log_type = K_LOG_STDERR;
? ? ? ? ? ? ? ? ? ? ? ? log_control.log_entries[i].lfu_fname =
? ? ? ? ? ? ? ? ? ? ? ? ? ? "standard error";
? ? ? ? ? ? ? ? ? ? }
? ? ? ? ? ? ? ? }
? ? ? ? ? ? ? ? /*
? ? ? ? ? ? ? ? ?* Is this a specification of the console?
? ? ? ? ? ? ? ? ?*/
? ? ? ? ? ? ? ? else if (!strcasecmp(cp, "CONSOLE")) {...}
? ? ? ? ? ? ? ? /*
? ? ? ? ? ? ? ? ?* Is this a specification of a device?
? ? ? ? ? ? ? ? ?*/
? ? ? ? ? ? ? ? else if (!strncasecmp(cp, "DEVICE", 6)) {...}

? ? ? ? ? ? ? ? /*
? ? ? ? ? ? ? ? ?* See if we successfully parsed this specification.
? ? ? ? ? ? ? ? ?*/
? ? ? ? ? ? ? ? if (log_control.log_entries[i].log_type == K_LOG_NONE) {
prints "cannot parse <STDERR>" ==>
? ? ? ? ? ? ? ? ? ? fprintf(stderr, lspec_parse_err_1, whoami, cp);
? ? ? ? ? ? ? ? ? ? fprintf(stderr, lspec_parse_err_2, whoami);
? ? ? ? ? ? ? ? }
? ? ? ? ? ? ? ? else
? ? ? ? ? ? ? ? ? ? ngood++;

--
vda


_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
Reply | Threaded
Open this post in threaded view
|

Re: [krbdev.mit.edu #3277] doubled kerberos logging to stderr

Greg Hudson via RT
>>>>> "Denis" == Denis Vlasenko via RT <[hidden email]> writes:

Denis> Looks like krb5-1.4.3/src/lib/kadm5/logger.c:klog_vsyslog(...) routine, which
Denis> formats these messages, outputs them twice.

Denis> Next, when I run exactly the same command, "krb5kdc -n", under daemontools,
Denis> it gets unhappy:

Denis> 2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
Denis> 2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error
Denis> 2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
Denis> 2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error

Denis> Replacing "default = STDERR" with "default = FILE:/proc/self/fd/2"
Denis> helps.

Denis> Fragment of strace output where it happens:

[...]

Denis> fcntl64(2, F_GETFL) ? ? ? ? ? ? ? ? ? ? = 0x1 (flags O_WRONLY)
Denis> write(2, "krb5kdc: cannot parse <STDERR>\n", 31) = 31
Denis> write(2, "krb5kdc: warning - logging entry"..., 46) = 46
Denis> fcntl64(2, F_GETFL) ? ? ? ? ? ? ? ? ? ? = 0x1 (flags O_WRONLY)
Denis> write(2, "krb5kdc: cannot parse <STDERR>\n", 31) = 31
Denis> write(2, "krb5kdc: warning - logging entry"..., 46) = 46

Denis> Looks like something fails here:

Denis> krb5-1.4.3/src/lib/kadm5/logger.c
Denis> ...
Denis> ? ? ? ? ? ? ? ? else if (!strcasecmp(cp, "STDERR")) {
Denis> ? ? ? ? ? ? ? ? ? ? log_control.log_entries[i].lfu_filep =
Denis> ? ? ? ? ? ? ? ? ? ? ? ? fdopen(fileno(stderr), "a+");
Denis> ? ? ? ? ? ? ? ? ? ? if (log_control.log_entries[i].lfu_filep) {
Denis> is not set somehow ===> log_control.log_entries[i].log_type = K_LOG_STDERR;
Denis> ? ? ? ? ? ? ? ? ? ? ? ? log_control.log_entries[i].lfu_fname =
Denis> ? ? ? ? ? ? ? ? ? ? ? ? ? ? "standard error";
Denis> ? ? ? ? ? ? ? ? ? ? }

While the error message is somewhat unhelpful, I suspect that the
actual error is that fdopen(fileno(stderr)) is failing for some
reason.  Fredrik Tolf, in a message to the kerberos mailing list,
appears to have discovered the actual reason for the doubled logs,
which is a configuration file being read twice under some
configurations.  What flags did you pass to configure when you built
the source?

---Tom

_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
Reply | Threaded
Open this post in threaded view
|

Re: [krbdev.mit.edu #3277] doubled kerberos logging to stderr

Greg Hudson via RT
In reply to this post by Greg Hudson via RT
On Wednesday 07 December 2005 02:01, Tom Yu via RT wrote:

> >>>>> "Denis" == Denis Vlasenko via RT <[hidden email]> writes:
>
> Denis> Looks like krb5-1.4.3/src/lib/kadm5/logger.c:klog_vsyslog(...) routine, which
> Denis> formats these messages, outputs them twice.
>
> Denis> Next, when I run exactly the same command, "krb5kdc -n", under daemontools,
> Denis> it gets unhappy:
>
> Denis> 2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
> Denis> 2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error
> Denis> 2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
> Denis> 2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error
>
> Denis> Replacing "default = STDERR" with "default = FILE:/proc/self/fd/2"
> Denis> helps.
>
> Denis> Fragment of strace output where it happens:
>
> [...]
>
> Denis> fcntl64(2, F_GETFL) ? ? ? ? ? ? ? ? ? ? = 0x1 (flags O_WRONLY)
> Denis> write(2, "krb5kdc: cannot parse <STDERR>\n", 31) = 31
> Denis> write(2, "krb5kdc: warning - logging entry"..., 46) = 46
> Denis> fcntl64(2, F_GETFL) ? ? ? ? ? ? ? ? ? ? = 0x1 (flags O_WRONLY)
> Denis> write(2, "krb5kdc: cannot parse <STDERR>\n", 31) = 31
> Denis> write(2, "krb5kdc: warning - logging entry"..., 46) = 46
>
> Denis> Looks like something fails here:
>
> Denis> krb5-1.4.3/src/lib/kadm5/logger.c
> Denis> ...
> Denis> ? ? ? ? ? ? ? ? else if (!strcasecmp(cp, "STDERR")) {
> Denis> ? ? ? ? ? ? ? ? ? ? log_control.log_entries[i].lfu_filep =
> Denis> ? ? ? ? ? ? ? ? ? ? ? ? fdopen(fileno(stderr), "a+");
> Denis> ? ? ? ? ? ? ? ? ? ? if (log_control.log_entries[i].lfu_filep) {
> Denis> is not set somehow ===> log_control.log_entries[i].log_type = K_LOG_STDERR;
> Denis> ? ? ? ? ? ? ? ? ? ? ? ? log_control.log_entries[i].lfu_fname =
> Denis> ? ? ? ? ? ? ? ? ? ? ? ? ? ? "standard error";
> Denis> ? ? ? ? ? ? ? ? ? ? }

Sorry about those "= = ="s, it's my KMail misbehaving...

> While the error message is somewhat unhelpful, I suspect that the
> actual error is that fdopen(fileno(stderr)) is failing for some
> reason.  Fredrik Tolf, in a message to the kerberos mailing list,
> appears to have discovered the actual reason for the doubled logs,
> which is a configuration file being read twice under some

It doesn't seem to be the case:

# grep open krb5kdc-n.strace
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
open("/usr/app/krb5-1.4.3/lib/i686/mmx/libkadm5srv.so.5", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/app/krb5-1.4.3/lib/i686/libkadm5srv.so.5", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/app/krb5-1.4.3/lib/mmx/libkadm5srv.so.5", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/app/krb5-1.4.3/lib/libkadm5srv.so.5", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libkdb5.so.4", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libgssrpc.so.4", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libgssapi_krb5.so.2", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libkrb4.so.2", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libdes425.so.3", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libkrb5.so.3", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libk5crypto.so.3", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libcom_err.so.3", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libkrb5support.so.0", O_RDONLY) = 3
open("/usr/app/krb5-1.4.3/lib/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
open("/lib/libc.so.6", O_RDONLY)        = 3
open("/etc/krb5.conf", O_RDONLY)        = 3
open("/dev/urandom", O_RDONLY)          = 3
open("/proc/self/fd/2", O_RDWR|O_APPEND|O_CREAT, 0666) = 3
open("/proc/self/fd/2", O_RDWR|O_APPEND|O_CREAT, 0666) = 4
open("/usr/app/krb5-1.4.3/var/krb5kdc/kdc.conf", O_RDONLY) = 5
open("/dev/urandom", O_RDONLY)          = 5
open("/usr/app/krb5-1.4.3/var/krb5kdc/kdc.conf", O_RDONLY) = 5
open("/var/service/kdc/.k5.LOCAL.NET", O_RDONLY) = 5
open("/var/service/kdc/principal", O_RDONLY) = 5
open("/var/service/kdc/principal.ok", O_RDWR) = 5
open("/var/service/kdc/principal", O_RDONLY) = 6
open("/var/tmp/krb5kdc_rcache", O_RDWR) = 6
open("/var/tmp/krb5kdc_rcache", O_RDWR) = 6
open("/var/tmp/krb5_RC1038aaa", O_WRONLY|O_CREAT|O_TRUNC|O_EXCL, 0600) = 7
open("/etc/localtime", O_RDONLY)        = 7

IOW, /etc/krb5.conf is read once, yet "default = FILE:/proc/self/fd/2"
directive seems to be processed twice.

> configurations.  What flags did you pass to configure when you built
> the source?

My configure invocation is:

SRC=..
STATIC=/usr/app/krb5-1.4.3
CFLAGS="-Os -falign-functions=1 -falign-labels=1 -falign-loops=1 -falign-jumps=1 -mtune=i386 -march=i386"
$SRC/configure \
--prefix=$STATIC                        \
--exec-prefix=$STATIC                   \
--bindir=$STATIC/bin                    \
--sbindir=$STATIC/sbin                  \
--libexecdir=$STATIC/libexec            \
--datadir=$STATIC/share                 \
--sysconfdir=/etc                       \
--sharedstatedir=$STATIC/var/com        \
--localstatedir=$STATIC/var             \
--libdir=$STATIC/lib                    \
--includedir=$STATIC/include            \
--infodir=$STATIC/info                  \
--mandir=$STATIC/man                    \
\
--oldincludedir=/usr/include            \
\
--build=i386-pc-linux-gnu               \
--disable-rpath                         \
--disable-nls

--
vda

_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
Reply | Threaded
Open this post in threaded view
|

Re: [krbdev.mit.edu #3277] doubled kerberos logging to stderr

Greg Hudson via RT
In reply to this post by Greg Hudson via RT
On Wednesday 07 December 2005 02:01, Tom Yu via RT wrote:

> Denis> Looks like krb5-1.4.3/src/lib/kadm5/logger.c:klog_vsyslog(...) routine, which
> Denis> formats these messages, outputs them twice.
>
> Denis> Next, when I run exactly the same command, "krb5kdc -n", under daemontools,
> Denis> it gets unhappy:
>
> Denis> 2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
> Denis> 2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error
> Denis> 2005-12-04 22:05:34 krb5kdc: cannot parse <STDERR>
> Denis> 2005-12-04 22:05:34 krb5kdc: warning - logging entry syntax error
>
> Denis> Replacing "default = STDERR" with "default = FILE:/proc/self/fd/2"
> Denis> helps.
>
...
>
> While the error message is somewhat unhelpful, I suspect that the
> actual error is that fdopen(fileno(stderr)) is failing for some
> reason.  Fredrik Tolf, in a message to the kerberos mailing list,
> appears to have discovered the actual reason for the doubled logs,
> which is a configuration file being read twice under some
> configurations.  What flags did you pass to configure when you built
> the source?

I instrumented code with a few a bit:

lib/kadm5/logger.c

    /*
     * Look up [logging]-><ename> in the profile.  If that doesn't
     * succeed, then look for [logging]->default.
     */
write(2, ename, strlen(ename));
write(2, "\n", strlen("\n"));
write(2, whoami, strlen(whoami));
write(2, "\n", strlen("\n"));
    logging_profent[0] = "logging";
    logging_profent[1] = ename;
    logging_profent[2] = (char *) NULL;
    logging_defent[0] = "logging";
    logging_defent[1] = "default";
    logging_defent[2] = (char *) NULL;
    logging_specs = (char **) NULL;
    ngood = 0;
    log_control.log_nentries = 0;
    if (/*!profile_get_values(kcontext->profile,
                            logging_profent,
                            &logging_specs) ||*/
        !profile_get_values(kcontext->profile,
                            logging_defent,
                            &logging_specs)) {
        /*
         * We have a match, so we first count the number of elements
         */
        for (log_control.log_nentries = 0;
             logging_specs[log_control.log_nentries];
             log_control.log_nentries++)
{
if(logging_specs[log_control.log_nentries]) write(2, logging_specs[log_control.log_nentries], strlen(logging_specs[log_control.log_nentries]));
write(2, "\n", strlen("\n"));
}
;

This is what my write's print:

kdc
krb5kdc
FILE:/proc/self/fd/2
FILE:/proc/self/fd/2

Obviously profile_get_values(kcontext->profile,
                            logging_defent,
                            &logging_specs) produces duplicates.
--
vda

_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
Reply | Threaded
Open this post in threaded view
|

Re: [krbdev.mit.edu #3277] doubled kerberos logging to stderr

Greg Hudson via RT
In reply to this post by Greg Hudson via RT
On Dec 7, 2005, at 02:38, Denis Vlasenko via RT wrote:
> On Wednesday 07 December 2005 02:01, Tom Yu via RT wrote:
>> While the error message is somewhat unhelpful, I suspect that the
>> actual error is that fdopen(fileno(stderr)) is failing for some
>> reason.  Fredrik Tolf, in a message to the kerberos mailing list,
>> appears to have discovered the actual reason for the doubled logs,
>> which is a configuration file being read twice under some
>
> It doesn't seem to be the case:

Actually, I think some of the code we've put into the profile library  
would prevent the file from being read twice if the stat data  
indicated it hadn't changed, even if the profile file names  
($KRB5_CONFIG or compiled-in) listed the same file twice.  The file  
would be read once, but its data would be used twice.

I'd be interested in seeing what profile_init is called with.

Ken

_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
Reply | Threaded
Open this post in threaded view
|

Re: [krbdev.mit.edu #3277] doubled kerberos logging to stderr

Greg Hudson via RT
In reply to this post by Greg Hudson via RT
>>>>> "Denis" == Denis Vlasenko via RT <[hidden email]> writes:

Denis> IOW, /etc/krb5.conf is read once, yet "default = FILE:/proc/self/fd/2"
Denis> directive seems to be processed twice.

If you set the KRB5_CONFIG environment variable to "/etc/krb5.conf",
do you still get the duplicates?

---Tom

_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
Reply | Threaded
Open this post in threaded view
|

Re: [krbdev.mit.edu #3277] doubled kerberos logging to stderr

Greg Hudson via RT
In reply to this post by Greg Hudson via RT
On Thursday 08 December 2005 19:39, Tom Yu via RT wrote:
> >>>>> "Denis" == Denis Vlasenko via RT <[hidden email]> writes:
>
> Denis> IOW, /etc/krb5.conf is read once, yet "default = FILE:/proc/self/fd/2"
> Denis> directive seems to be processed twice.
>
> If you set the KRB5_CONFIG environment variable to "/etc/krb5.conf",
> do you still get the duplicates?

No, I do not. This is instrumented version of kdc running:

2005-12-09 10:02:54.655785500 kdc
2005-12-09 10:02:54.656054500 krb5kdc
2005-12-09 10:02:54.656147500 FILE:/proc/self/fd/2   <=== parses config
2005-12-09 10:02:54.656335500 FILE
2005-12-09 10:02:55.046682500 !    <=== about to emit message
2005-12-09 10:02:55.046787500 *    <=== one and only log destination
2005-12-09 10:02:55.046991500 Dec 09 10:02:55 logic krb5kdc[4905](info): setting up network...
2005-12-09 10:02:55.047331500 !
2005-12-09 10:02:55.047390500 *
2005-12-09 10:02:55.047447500 Dec 09 10:02:55 logic krb5kdc[4905](info): listening on fd 6: udp 172.16.22.2.750
2005-12-09 10:02:55.047551500 !
2005-12-09 10:02:55.047632500 *
2005-12-09 10:02:55.047688500 Dec 09 10:02:55 logic krb5kdc[4905](info): listening on fd 7: udp 172.16.22.2.88
...

Without KRB5_CONFIG:

2005-12-08 14:46:04.467856500 kdc
2005-12-08 14:46:04.468130500 krb5kdc
2005-12-08 14:46:04.468231500 FILE:/proc/self/fd/2   <=== parses config, gets FILE:... twice
2005-12-08 14:46:04.468306500 FILE:/proc/self/fd/2
2005-12-08 14:46:04.468521500 FILE
2005-12-08 14:46:04.468613500 FILE
2005-12-08 14:46:04.814418500 !    <=== about to emit message
2005-12-08 14:46:04.814508500 *    <=== log to first FILE:
2005-12-08 14:46:04.814616500 Dec 08 14:46:04 logic krb5kdc[31794](info): setting up network...
2005-12-08 14:46:04.814678500 *    <=== log to second FILE:
2005-12-08 14:46:04.814758500 Dec 08 14:46:04 logic krb5kdc[31794](info): setting up network...
...

--
vda

_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs