search for: elogs

Denny: Thank you. Problem solved. I switched SHUTDOWNCMD back to the default and added nut.powerfail to the shutdown runlevel. Now the UPS turns off after the system shutdown, if the shutdown is caused by lack of power going to the UPS. I checked and found the file sys-power:nut-2.7.4-r1:2018...log in /var/log/portage/elog/*. It did contain the message you pointed out. I should have checked

Glad you got it working. Denny > On Jul 28, 2018, at 19:02, richjunk at pacbell.net wrote: > > Denny: > > Thank you. Problem solved. > > I switched SHUTDOWNCMD back to the default and added nut.powerfail to > the shutdown runlevel. Now the UPS turns off after the system shutdown, > if the shutdown is caused by lack of power going to the UPS. > > I checked

...EGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i got a problem with dovecot 0.99.14 - after a while of checking pop3 periodically, the dovecot-auth process gets killed. Some clients, e.g. outlook (express), then requests for reentering the password. When this happens, i see something like this in th elogs: Apr 28 14:53:45 marge dovecot: child 25819 (auth) killed with signal 4 Apr 28 14:55:09 marge dovecot: login: received another "not listening" notification (if you can't login at all, see src/lib/fdpass.c) Any idea, how to solve this? Thanks in advance, Andreas Goertz. -----BEGIN P...

I do not know if this is a help request to solve a problem but to understand what is going on. I am going to start with the problem description as I see it and we will go from there. I have postfix setup to use dovecot for tls/sasl in addition to its normal imap/pop3 functions. Postfix is also setup to do virtual domains, getting its information from the files valias, vmaps, and vhosts which are

I just installed NUT on a new Linux (Gentoo) system. Most things work, (notification after 10 seconds on battery, notification and system shutdown after 100 seconds on battery.) However I can't seem to get the UPS (an Eaton 5SC1500) to turn itself off after the Gentoo system shutdown. This is the shutdown command I am using in /etc/nut/upsmon.conf: SHUTDOWNCMD "/usr/sbin/upsdrvctl

/* * Copyright (c) 1983, 1995, 1996 Eric P. Allman * Copyright (c) 1988, 1993 * The Regents of the University of California. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of

On Thu, Sep 3, 2015 at 6:45 PM, Kostya Serebryany <kcc at google.com> wrote: > Did you build the Postgres code with -fsanitize-coverage=... ? Yes: CC = clang CFLAGS = -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -Wno-unused-command-line-argument -g -O0 -fsanitize=address

Looks correct. Can you post the output of libFuzzer here? Something like #0 READ cov: 0 bits: 0 units: 97701 exec/s: 0 #1 pulse cov: 732 bits: 0 units: 97701 exec/s: 0 #2 pulse cov: 737 bits: 0 units: 97701 exec/s: 1 #4 pulse cov: 858 bits: 0 units: 97701 exec/s: 2 #8 pulse cov: 880 bits: 0 units: 97701 exec/s: 4 On Thu, Sep 3, 2015 at 10:50 AM, Greg Stark

...ly passed to 2.2.1a, but this prble was alway spresente also with 2.2.0 and 2.0.7 (statiscs say lower times than now). Three pces worsk on a share, with a sort of db (IDOL-VI) and lock soem files to upgrade. The system works well, but sometimes, not even periodci, the three sysems blocks, and on th elogs the only things that i see, is this : [2001/09/10 11:37:30, 0] smbd/oplock.c:request_oplock_break(997) request_oplock_break: no response received to oplock break request to pid 4715 on port 1046 for dev = 804, inode = 83759 for dev = 804, inode = 83759, tv_sec = 3b9c89ba, tv_usec = 3e163 [200...

...this prble was alway spresente > also with 2.2.0 and 2.0.7 (statiscs say lower times than now). > Three pces worsk on a share, with a sort of db (IDOL-VI) and lock soem > files to upgrade. > The system works well, but sometimes, not even periodci, the three > sysems blocks, and on th elogs the only things that i see, is this : > > [2001/09/10 11:37:30, 0] smbd/oplock.c:request_oplock_break(997) > request_oplock_break: no response received to oplock break request to > pid 4715 > on port 1046 for dev = 804, inode = 83759 > for dev = 804, inode = 83759, tv_sec = 3...