search for: 17966

...og/dovecot-err.log: Permission denied ) But, log files seems ok: -rw------- 1 777 root 56 Oct 8 10:35 dovecot-err.log -rw------- 1 777 root 302 Oct 8 10:35 dovecot-inf.log Also processess seems right: root 17965 0.0 0.0 2052 584 ? Ss 10:35 0:00 /usr/sbin/dovecot root 17966 0.0 0.2 8564 2172 ? S 10:35 0:00 dovecot-auth root 17967 0.0 0.2 8564 2356 ? S 10:35 0:00 dovecot-auth -w dovecot 17969 0.0 0.1 3476 1572 ? S 10:36 0:00 pop3-login dovecot 17970 0.0 0.1 3476 1572 ? S 10:36 0:00 pop3-login dov...

...ug1: channel 0: read failed debug1: channel 0: input open -> drain debug1: channel 0: close_read debug1: channel 0: input: no drain shortcut debug1: channel 0: ibuf empty debug1: channel 0: input drain -> closed debug1: channel 0: send eof debug1: Received SIGCHLD. debug1: session_by_pid: pid 17966 debug1: session_exit_message: session 0 channel 0 pid 17966 debug1: session_exit_message: release channel 0 debug1: channel 0: write failed debug1: channel 0: output open -> closed debug1: channel 0: close_write debug1: session_pty_cleanup: session 0 release /dev/pts/1 debug1: session_free: sess...

...ecot: auth(default): master out: USER 1 ohp system_user=ohp uid=101 gid=130 home=/home4/ohp Jan 24 14:59:47 dovecot: imap-login: Login: user=<ohp>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 14:59:47 dovecot: imap(ohp): Trying to allocate 0 bytes Jan 24 14:59:47 dovecot: child 17966 (imap) killed with signal 6 Jan 24 15:22:08 dovecot: imap-login: Disconnected: rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 15:29:04 dovecot: SIGHUP received - reloading configuration Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Ja...

...127 named groups (PR#18588). * Datetime functions are now robust against long jumps when dealing with internal time zone changes. This avoids confusing warnings about an invalid time zone, previously triggered by turning warnings into errors or handling them via tryCatch (PR#17966, PR#17780). * Datetime functions now restore even an empty TZ environment variable after internal time zone changes (PR#17724). This makes results of datetime functions with this (typically unintentional) setting more predictable. * drop.terms(*) now drops respons...

...127 named groups (PR#18588). * Datetime functions are now robust against long jumps when dealing with internal time zone changes. This avoids confusing warnings about an invalid time zone, previously triggered by turning warnings into errors or handling them via tryCatch (PR#17966, PR#17780). * Datetime functions now restore even an empty TZ environment variable after internal time zone changes (PR#17724). This makes results of datetime functions with this (typically unintentional) setting more predictable. * drop.terms(*) now drops respons...

...#39;t said this - blyat! (this is in russian ;) ). OK. Removing locking.tdb, I don't know what else I can do. And killing my smbd. Oops! I see two smd for me in smbd status! PC$ dm dm 17909 dm-w2k (192.168.21.112) Wed May 16 09:45:06 2001 print$ dm dm 17966 dm-w2k (192.168.21.112) Wed May 16 09:47:58 2001 ?????? Well, now all is OK. Full log (gzipped) is attached. Hope that this help to find bug in locking. -- Wire connection and Windows reinstallation senior engineer Dmitry Melekhov http://www.belkam.com/~dm 2:5050/11.23@fidonet [demime 0.9...