From: Robert Vollmert <rob@vllmrt.net>
To: 36838@debbugs.gnu.org
Subject: bug#36838: mcron leaves zombies around
Date: Mon, 29 Jul 2019 17:39:33 +0200 [thread overview]
Message-ID: <70F6F2EB-3619-4175-885F-C970448355D7@vllmrt.net> (raw)
It seems that mcron doesn’t clean up after itself. I regularly see
some zombie processes around, presumably left over by each of my
two 15-minute cron jobs:
root 21285 0.0 0.3 24124 3248 ? Ss 11:05 0:00 /gnu/store/mamwayq00mqs85kgs6ibww7xw6dy776s-mcron-1.1.1/bin/mcron /gnu/store/rdi71izz4d16v77hb8h2jks0s3q9zini-mcron-job /gnu/store/k7dn1v7qpi4kz183glmbgsf1c7pj19xx-mcron-job /gnu/store/lfyj23bzhc14y5rqi91g493jql9dphxk-mcron-job /gnu/store/mx9k5n92kmhryn3vh4607hrmnkjb8dl6-mcron-job /gnu/store/l4nxmajr0i5g07fxvrgnaw29zd1jq0qw-mcron-job
root 26611 0.0 0.0 0 0 ? Z 17:29 0:00 [mcron] <defunct>
root 26612 0.0 0.0 0 0 ? Z 17:29 0:00 [mcron] <defunct>
In case that matters, they’re defined using the following:
(define puzzledb-tweets-pzv-job
(let* ((exp
(with-imported-modules '((helpers))
#~(begin
(use-modules (helpers))
(let ((backend (read-secret "tools.jwt"))
(twitter (read-secret "twitter.token")))
(runl (string-append #$puzzledb-tools "/bin/tweets")
"-backend_token" backend
"-token" twitter
"-deletes")))))
(script (program-file "puzzledb-tweets-pzv-job" exp)))
#~(job "*/15 * * * *" ; every fifteen minutes
#$script)))
where the module helpers contains:
(define-module (helpers)
#:use-module (ice-9 textual-ports)
#:export (runl read-secret))
(define* (runl prog . args)
(apply execl prog prog args))
(define* (read-secret file)
(string-trim-both
(get-string-all
(open-input-file
(string-append "/etc/puzzledb/secrets/" file)))))
next reply other threads:[~2019-07-29 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 15:39 Robert Vollmert [this message]
2021-08-24 3:55 ` bug#36838: mcron leaves zombies around Maxim Cournoyer
2021-08-24 10:12 ` Leo Prikler
2021-08-29 21:35 ` Maxim Cournoyer
2023-07-20 13:19 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70F6F2EB-3619-4175-885F-C970448355D7@vllmrt.net \
--to=rob@vllmrt.net \
--cc=36838@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).