Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 5323 - at now and batch commands
at now and batch commands
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: at (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 1999-09-23 08:41 EDT by paulh
Modified: 2014-03-16 22:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-28 11:35:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description paulh 1999-09-23 08:41:28 EDT 
The at now command does not work.

    echo "date" | at now

will never schedule execution. It seems that the job is
scheduled a few seconds *before* the current time.

As a consequence the 'batch' command does not work as it is
a script that executes at now.

Interestingly I have seen this same bug in IRIX,CLIX,AIX,
etc. The solution is to add 1 or 2 minutes depending on
the version of UNIX. This is because some at commands only
schedule to the nearest minute boundary viz

    echo "date" | at now + 2 minutes
Comment 1 Bernhard Rosenkraenzer 2000-02-16 09:07:59 EST 
Still happens in 6.2b3 - "now" apparently maps to `date  +%H:%M`, so seconds are
lost -> scheduled before current time.
Comment 2 Bill Nottingham 2000-02-16 15:42:59 EST 
Hmm.. it works OK for me here; at now casues
things to be run immediately.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.