Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779583
Title:
cron
** Tags removed: trusty
** Tags added: xenial
** Description changed:
The do_command.c file calls fork() twice.
For the first fork(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779583
Title:
cron do_command.c attempts a fork() without testing for errors
To manage notifications about this bug go to:
https
The attachment "Compiling fix to second fork() in child_process()" seems
to be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Lau
I guess I should attempt to compile before submitting a patch. Some
brackets were required in one of the cases.
** Patch added: "Compiling fix to second fork() in child_process()"
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+attachment/5158458/+files/do_command-2.patch
--
You
** Description changed:
The do_command.c file calls fork() twice.
- For the first for(), the possibility for an error is checked properly
+ For the first fork(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/
This may be one solution to the problem reported here:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785
Because when the second fork() fails, the cron process waits for 2
children, one of which doesn't even exist and thus cron is stuck with "a
ton" of memory allocated. This would also
