RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 970136 [details]
Upstream-derived patch that prevents crashes

This is the duplicate of a support case ticket of mine, so that non-customers can see it too. I reported this issue for 6.3 and it is still present. I don't know what Redhat's experimental solution was to the problem, as they could not provide a SRPM. I don't know if it happens on every architecture, but it certainly does on x86_64. The attached patch works for me.

"""
Atd crashed for the second time in the course of a few weeks. Knowingly, I only use it to run jobs as one specific unpriviledged user, a couple of thousand times a day: echo "mycommand_and_options > /dev/null 2>&1" | at now Abrt is quiet about the crash.

The messages log only indicates: atd[2712]: Can't link execution file: No such file or directory

The problem is also a bit nasty, because at still accepts new jobs and only puts them in the queue.
"""

"""
At the end of the day, it's a root-run daemon, some people rely on. It can be "crashed" by an unprivileged user within 15 seconds and it doesn't leave a distinctive trace when it happens.
"""

Upstream ticket, solved in 3.13:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309014

https://access.redhat.com/support/cases/#/case/00746100

Fixed by 
https://rhn.redhat.com/errata/RHBA-2015-0240.html

this bug has been fixed , so closing