search for: loiter

...xplaining what happens and why :) Possibly there was a child or CLI counterpart process which died and somehow the connection did not get closed (which would return a `read()` error and evict it from the conn list), e.g. frozen/zombified, or something else connected to the pipe (antivirus heh?) and loiters there, or something else I could not think of quickly... The next clue could be to look at who is connected to the pipe file, maybe with `fuser`, or look in `ps -ef` if there are other `upssched` processes present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping `upssched`... If anyo...

...xplaining what happens and why :) Possibly there was a child or CLI counterpart process which died and somehow the connection did not get closed (which would return a `read()` error and evict it from the conn list), e.g. frozen/zombified, or something else connected to the pipe (antivirus heh?) and loiters there, or something else I could not think of quickly... The next clue could be to look at who is connected to the pipe file, maybe with `fuser`, or look in `ps -ef` if there are other `upssched` processes present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping `upssched`... If anyo...

Hi, Indeed, and I think this suggestion will succeed best if the delta between what community members do now and what they would need to do is small. Loitering on one extra IRC room is trivial; loading a whole new system just at the right time is likely to get fewer members. James On Sun, 20 Mar 2016 at 14:47, Bruce Hoult <bruce at hoult.org> wrote: > IRC doesn't archive messages, but many IRC communities run a bot as a room > partici...

...ns and > why :) Possibly there was a child or CLI counterpart process which died and > somehow the connection did not get closed (which would return a `read()` > error and evict it from the conn list), e.g. frozen/zombified, or something > else connected to the pipe (antivirus heh?) and loiters there, or something > else I could not think of quickly... > > The next clue could be to look at who is connected to the pipe file, maybe > with `fuser`, or look in `ps -ef` if there are other `upssched` processes > present, or look in `/proc/PIDNUM/fd/` of the daemonized and loopin...

...ns and > why :) Possibly there was a child or CLI counterpart process which died and > somehow the connection did not get closed (which would return a `read()` > error and evict it from the conn list), e.g. frozen/zombified, or something > else connected to the pipe (antivirus heh?) and loiters there, or something > else I could not think of quickly... > > The next clue could be to look at who is connected to the pipe file, maybe > with `fuser`, or look in `ps -ef` if there are other `upssched` processes > present, or look in `/proc/PIDNUM/fd/` of the daemonized and loopin...

Hi all! I'm trying to build the buoh comic reader for centos 6 and my head is getting tired of repeated forceful contact with the wall. I built it on 5.6 without undue problems, but somehow 6.0 is beating me. (and no, the 5.6 binary doesn't work, at least not without a lot of futzing around, on 6.0. tried that first.) before I give gory details, has anyone already done this, from whom

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

@James I am not sure in IRC if we can retrieve back the older messages. So consider Slack as suggestion only. *Vivek Pandya* On Sun, Mar 20, 2016 at 6:29 PM, James Molloy <james at jamesmolloy.co.uk> wrote: > Hmm. But we already use IRC, we don't already use Slack (as a community). > > On Sun, 20 Mar 2016 at 10:57, vivek pandya <vivekvpandya at gmail.com> wrote: >

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''