I got my zombies from libpam-ssh
--
cron's immediate child becomes a zombie process
https://bugs.launchpad.net/bugs/137785
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Confirming this one.
I just discovered a boat-load of sh zombies on one of my Karmic-boxes,
and they are all descendants of the cron daemon. I'm also getting the
Skipping automatic eCryptfs mount CRON message in syslog. I have
eCryptfs set up to *not* auto-mount the ~/Private directory on login.
This bug is most likely not in cron. The integration of eCryptfs in PAM
is causing problems elsewhere as well. If I log out from a VC and have
an ~/.ecryptfs directory, then logout behaves weirdly, and I have to
quit *two* shells, before I'm actually logged out. A security issue, if
you ask me.
Cron jobs exit normally when I enable the ~/.ecryptfs/auto-mount option.
** Changed in: ecryptfs
Status: New = Invalid
--
cron's immediate child becomes a zombie process
https://bugs.launchpad.net/bugs/137785
You received this bug notification because you are a member of Ubuntu
Bugs,
Sorry, this particular bug report isn't suitable for the ecryptfs-
issues, I'll file a new one..
--
cron's immediate child becomes a zombie process
https://bugs.launchpad.net/bugs/137785
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since upgrading to karmic I encountered a problem that seems to be
similar to this bug:
- I had to manually restart cron after every reboot to get cronjobs
started at all.
- I had to restart cron regularly to get rid of the zombies.
Today I found a solution that seems to work for me. I found
** Changed in: cron (Ubuntu)
Status: New = Confirmed
--
cron's immediate child becomes a zombie process
https://bugs.launchpad.net/bugs/137785
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi!
I do have ssmtp set up to use a postfix server for my domain and
directed both STDERR and STDOUT to /dev/null so there *should* have been
no output to be mailed. To skirt the problem in my post, I decided to
use the autossh package to do the redialing on ssh and wrapped it in a
shell
Hello !
I think i have the same problem as you. When cron starts a cronjob from a user
for example,
that returns more than just a status, for example, wget something, than cron
starts a child process
that is cron defunced from the start and exits a few seconds later, even if
the shell script
