Displaying 20 results from an estimated 305 matches for "reap".
Did you mean:
read
2013 Oct 07
4
AutoBL issues on CentOS 6
...rewall::Config;
+
my ( $event, $interval, $count, $successive, $bltime, $disposition,
$level ) = get_action_params(7);
fatal_error "The event name parameter to AutoBL is required"
unless supplied $event;
2) The iptables package of CentOS 6 doesn''t have the "--reap" option. From
some Google searches it seems that the same applies to a number of
distributions and iptables version, even new iptables versions. My
question is, is there a way to change action.IfEvent to work without the
"--reap" option?
Thanks,
Simon
-----------------------------...
2019 Jan 25
0
[klibc:update-dash] eval: Reap zombies after built-in commands and functions
...g/?p=libs/klibc/klibc.git;a=commit;h=ed1a1311732c764495a5ec26bfdcac34ea6dce1b
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 26 Mar 2018 23:55:50 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Fri, 25 Jan 2019 02:57:21 +0000
[klibc] eval: Reap zombies after built-in commands and functions
Currently dash does not reap dead children after built-in commands
or functions. This means that if you construct a loop consisting
of solely built-in commands and functions, then zombies can hang
around indefinitely.
This patch fixes this by reaping...
2020 Mar 28
0
[klibc:update-dash] dash: eval: Reap zombies after built-in commands and functions
...ibs/klibc/klibc.git;a=commit;h=a33ea92e57007317a5c406626441029899e164e0
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 26 Mar 2018 23:55:50 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:54 +0000
[klibc] dash: eval: Reap zombies after built-in commands and functions
[ dash commit 03876c0743a50984b0aae69bba6f5034dc38aec1 ]
Currently dash does not reap dead children after built-in commands
or functions. This means that if you construct a loop consisting
of solely built-in commands and functions, then zombies can h...
2010 May 05
1
[PATCH 1/2] reap the blktapctl thread and notify the tapdisk backend driver to release resource like memory..
...n/xend/image.py Tue May 04 13:59:55 2010 +0100
+++ b/tools/python/xen/xend/image.py Wed May 05 10:46:52 2010 +0800
@@ -629,30 +629,6 @@
os.kill(self.pid, signal.SIGHUP)
except OSError, exn:
log.exception(exn)
- # Try to reap the child every 100ms for 10s. Then SIGKILL it.
- for i in xrange(100):
- try:
- (p, rv) = os.waitpid(self.pid, os.WNOHANG)
- if p == self.pid:
- break
- except OSError:
-...
2016 Jun 19
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
...dex 6d81a1eb974a..2b00ac7faa18 100644
> > --- a/include/linux/sched.h
> > +++ b/include/linux/sched.h
> > @@ -513,6 +513,7 @@ static inline int get_dumpable(struct mm_struct *mm)
> > #define MMF_RECALC_UPROBES 20 /* MMF_HAS_UPROBES can be wrong */
> > #define MMF_OOM_REAPED 21 /* mm has been already reaped */
> > #define MMF_OOM_NOT_REAPABLE 22 /* mm couldn't be reaped */
> > +#define MMF_UNSTABLE 23 /* mm is unstable for copy_from_user */
> >
> > #define MMF_INIT_MASK (MMF_DUMPABLE_MASK | MMF_DUMP_FILTER_MASK)
> >
> >...
2016 Jun 19
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
...dex 6d81a1eb974a..2b00ac7faa18 100644
> > --- a/include/linux/sched.h
> > +++ b/include/linux/sched.h
> > @@ -513,6 +513,7 @@ static inline int get_dumpable(struct mm_struct *mm)
> > #define MMF_RECALC_UPROBES 20 /* MMF_HAS_UPROBES can be wrong */
> > #define MMF_OOM_REAPED 21 /* mm has been already reaped */
> > #define MMF_OOM_NOT_REAPABLE 22 /* mm couldn't be reaped */
> > +#define MMF_UNSTABLE 23 /* mm is unstable for copy_from_user */
> >
> > #define MMF_INIT_MASK (MMF_DUMPABLE_MASK | MMF_DUMP_FILTER_MASK)
> >
> >...
2007 Feb 26
2
Apache+mod_proxy_balancer+Mongrel+Mephisto, Apache kills CPU
...ect_key__, :started_on]
-- #<Thread:0x36f8c78>: [:__inspect_key__, :started_on]
-- #<Thread:0x35e352c>: [:__inspect_key__, :started_on]
[Excerpt from mongrel.log when killing unresponsive mongrels]
** TERM signal received.
Mon Feb 26 14:37:06 PST 2007: Reaping 3 threads for slow workers
because of ''shutdown''
Waiting for 3 requests to finish, could take 60 seconds.object.log
ERROR: undefined method `class'' for #<Liquid::Strainer:0x3132ba4>
object.log ERROR: undefined method `class'' for #<Liquid::Strainer...
2013 Jan 24
2
SIGSEGV at shutdown (was: Re: your mail)
...t;charles.hornberger at gmail.com> wrote:
>> Hi!
>>
>> I recently noticed this error message when restarting unicorn after a
>> code deployment (and I don''t think I recall having seen it before):
>>
>> I, [2013-01-18T17:54:21.502554 #59285] INFO -- : reaped
>> #<Process::Status: pid 59293 exit 0> worker=6
>> I, [2013-01-18T17:54:21.502692 #59285] INFO -- : reaped
>> #<Process::Status: pid 59294 exit 0> worker=7
>> I, [2013-01-18T17:54:21.502754 #59285] INFO -- : reaped
>> #<Process::Status: pid 59292 ex...
2001 Jan 25
1
rcmd build
I''m having trouble building a package (named reap) under R1.2.1 Windows2000. I
successfully ran
d:\R\src\library rcmd check reap
but when I run
d:\R\src\library rcmd build reap
I get the message:
Please set TMPDIR to a valid temporary directory
I''ve tried setting TMPDIR to d:/temp via:
1) My Computer properties environment variables,
2)...
2016 Dec 13
15
[Bug 2646] New: zombie processes when using privilege separation
...Component: sshd
Assignee: unassigned-bugs at mindrot.org
Reporter: akshay.moghe at gmail.com
I'm using `OpenSSH_7.2p2 Ubuntu-4ubuntu1, OpenSSL 1.0.2g-fips` and I've
explicitly enabled UsePrivilegeSeparation.
With this I notice that the [priv] process does not get reaped by its
parent (sshd) and as a result is adopted by whatever pid 1 happens to
be. Normally this is okay since most init systems will handle this
correctly, however in containers we might encounter homemade "init"
systems that only serve to propagate signals but don't reap adopted
zom...
2011 Dec 08
5
Master repeatedly killing workers due to timeouts
...mber of times in
the past few days, our unicorn slaves keep timing out & the master
keeps restarting them. unicorn.log looks something like :
E, [2011-12-08T18:11:32.912237 #26661] ERROR -- : worker=5 PID:15367
timeout (61s > 60s), killing
E, [2011-12-08T18:11:32.952041 #26661] ERROR -- : reaped
#<Process::Status: pid 15367 SIGKILL (signal 9)> worker=5
I, [2011-12-08T18:11:32.985925 #17824] INFO -- : worker=5 ready
E, [2011-12-08T18:11:42.962869 #26661] ERROR -- : worker=3 PID:15499
timeout (61s > 60s), killing
E, [2011-12-08T18:11:43.003741 #26661] ERROR -- : reaped
#<Proce...
2006 Jan 29
8
Infinite loop shutting down xendomains
...''vpn1dc1'', ''2'', ''halt'']
[2006-01-28 22:06:09 xend] INFO (XendRoot:113) EVENT>
xend.domain.shutdown [''niagras1'', ''1'', ''halt'']
[2006-01-28 22:06:22 xend] DEBUG (XendDomain:244) XendDomain>reap>
domain died name=niagras1 id=1
[2006-01-28 22:06:22 xend] DEBUG (XendDomain:247) XendDomain>reap>
shutdown id=1 reason=poweroff
[2006-01-28 22:06:22 xend] DEBUG (XendDomain:487)
domain_restart_schedule> 1 poweroff 0
[2006-01-28 22:06:22 xend] INFO (XendDomain:568) Destroying domain:
na...
2019 Sep 06
0
possible deadlock in __mmu_notifier_invalidate_range_end
...03250fe1f at syzkaller.appspotmail.com
Fixes: e58b341134ca ("Merge remote-tracking branch 'hmm/hmm'")
============================================
WARNING: possible recursive locking detected
5.3.0-rc6-next-20190830 #75 Not tainted
--------------------------------------------
oom_reaper/1065 is trying to acquire lock:
ffffffff8904ff60 (mmu_notifier_invalidate_range_start){+.+.}, at:
__mmu_notifier_invalidate_range_end+0x0/0x360 mm/mmu_notifier.c:169
but task is already holding lock:
ffffffff8904ff60 (mmu_notifier_invalidate_range_start){+.+.}, at:
__oom_reap_task_mm+0x196/0...
1999 Nov 20
1
openssh and DOS
...I am posting
this here in the hopes that a good solution can be found that can
be passed on to the openbsd people.
There is a related problem I noticed when doing this. If I open a
bunch of connections to ssh (say in a perl script) and then close
them all at once only some of the children get reaped on the server.
The reason for this seems to be that in the SIGCHLD handler,
main_sigchld_handler, uses a wait call to reap one child. If you
have multiple children dying at roughly the same time some do not
get caught by the handler and thus not reaped. They remain as
zombies until sshd is re...
2016 Jun 17
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
From: Michal Hocko <mhocko at suse.com>
vhost driver relies on copy_from_user/get_user from a kernel thread.
This makes it impossible to reap the memory of an oom victim which
shares mm with the vhost kernel thread because it could see a zero
page unexpectedly and theoretically make an incorrect decision visible
outside of the killed task context.
Make sure that each place which can read from userspace is annotated
properly and it uses...
2016 Jun 17
2
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
From: Michal Hocko <mhocko at suse.com>
vhost driver relies on copy_from_user/get_user from a kernel thread.
This makes it impossible to reap the memory of an oom victim which
shares mm with the vhost kernel thread because it could see a zero
page unexpectedly and theoretically make an incorrect decision visible
outside of the killed task context.
Make sure that each place which can read from userspace is annotated
properly and it uses...
2016 Jan 29
2
Zombie processes being created when console buffer is full
...here was 1 thread and it was waiting in
write() and the file being written was /dev/console.
This write() to the console never returns. We operated under the
assumption that systemd's SIGCHLD handler sets a bit and a foreground
thread (the only thread) would see that child processes needed reaping.
While the single thread is stuck in write(), the reaping never takes
place.
So why is write() blocking? The answer seems to be that there is
nothing draining the console and eventually it blocks write() when its
buffers become full. When we attached to the container's console, the...
2023 Sep 08
1
[PATCH V3] io_uring: fix IO hang in io_wq_put_and_exit from do_exit()
...t;
> >>
> >>> @@ -3363,6 +3367,12 @@ __cold void io_uring_cancel_generic(bool cancel_all, struct io_sq_data *sqd)
> >>> finish_wait(&tctx->wait, &wait);
> >>> } while (1);
> >>>
> >>> + /*
> >>> + * Reap events from each ctx, otherwise these requests may take
> >>> + * resources and prevent other contexts from being moved on.
> >>> + */
> >>> + xa_for_each(&tctx->xa, index, node)
> >>> + io_iopoll_try_reap_events(node->ctx);
> >>...
2023 Sep 08
1
[PATCH V3] io_uring: fix IO hang in io_wq_put_and_exit from do_exit()
...t;
> >>
> >>> @@ -3363,6 +3367,12 @@ __cold void io_uring_cancel_generic(bool cancel_all, struct io_sq_data *sqd)
> >>> finish_wait(&tctx->wait, &wait);
> >>> } while (1);
> >>>
> >>> + /*
> >>> + * Reap events from each ctx, otherwise these requests may take
> >>> + * resources and prevent other contexts from being moved on.
> >>> + */
> >>> + xa_for_each(&tctx->xa, index, node)
> >>> + io_iopoll_try_reap_events(node->ctx);
> >>...
2016 Jun 18
0
[RFC PATCH] vhost, mm: make sure that oom_reaper doesn't reap memory read by vhost
On Fri, Jun 17, 2016 at 11:00:17AM +0200, Michal Hocko wrote:
> From: Michal Hocko <mhocko at suse.com>
>
> vhost driver relies on copy_from_user/get_user from a kernel thread.
> This makes it impossible to reap the memory of an oom victim which
> shares mm with the vhost kernel thread because it could see a zero
> page unexpectedly and theoretically make an incorrect decision visible
> outside of the killed task context.
>
> Make sure that each place which can read from userspace is annota...