Bug 244844 - at/batch won't deliver email
at/batch won't deliver email
Status: CLOSED DUPLICATE of bug 243064
Product: Fedora
Classification: Fedora
Component: at (Show other bugs)
i386 Linux
low Severity high
: ---
: ---
Assigned To: Marcela Mašláňová
Depends On:
  Show dependency treegraph
Reported: 2007-06-19 09:57 EDT by ptomblin
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-25 09:24:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description ptomblin 2007-06-19 09:57:11 EDT
Description of problem:
When the at/batch job finishes, the attempt to deliver the email fails with the
message "Jun 19 09:24:58 allhats atd[19566]: Open of jobfile failed: Success"
and then atd dies.

Version-Release number of selected component (if applicable):

How reproducible:
Every time.

Steps to Reproduce:
1. Submit a batch job that produces email, like "echo 'yes'"
2. Restart service atd if it's dead

Actual results:
atd is dead.
The message "atd[19504]: Open of jobfile failed: Success" is in /var/log/messages
The actual output of the at job is in /var/spool/at/spool.
The batch job file is still in /var/spool/at

Expected results:
An email is sent to me.
atd continues to run.
The message and job files are cleaned up from their respective directories.

Additional info:
Comment 1 ptomblin 2007-06-21 17:03:47 EDT
Not sure if it's relevant, but this system has been progressively upgraded from
RedHat 6 or so, and had only just been upgraded from Fedora Core 5 to Fedora 7.
Comment 2 Steve Stavropoulos 2007-06-23 18:55:14 EDT
This same bug is described here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243064 and here: 
Comment 3 Marcela Mašláňová 2007-06-25 09:24:22 EDT

*** This bug has been marked as a duplicate of 243064 ***

Note You need to log in before you can comment on or make changes to this bug.