Defect report from : Andrew Josey , The Open Group
(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)
@ page 144 line 5501 section at objection {AI-2006-02-08}
Problem:
Edition of Specification (Year): 2004
Defect code : 1. Error
In the scope for the revision we have:
The revision will review the use of fixed path filenames within the
standard, for example the at, batch and crontab utilities
that presently have a requirement for use of the directory /usr/lib/cron
The at, batch and crontab utilities all reference files in a fixed location
(/usr/lib/cron). There is thought to be little benefit to portable applications
for naming the location of these files. Its also
possible to argue that these are system administration rather than for portable
application usage.
Action:
There are two possible options here
(a) Removing mention of the files altogether, replacing the XSI
shaded text in DESCRIPTION with regular unshaded text.
"There may be implementation-defined restrictions that determine whether a user
is permitted to use the at utility."
Remove the XSI shaded text in INPUT FILES
(repeat also for batch and crontab, edited as appropriate)
or
(b)It is proposed that the location of these files be made
implementation-defined. In which case
change in the XSI shaded text in DESCRIPTION
"the file /usr/lib/cron/at.allow"
to
"the file at.allow which is located in an implementation-defined directory".
change
"the file /usr/lib/cron/at.deny shall be checked"
to
"the file at.deny, which is located in an implementation-defined directory,
shall be checked"
In INPUT FILES
Change
"The text files /usr/lib/cron/at.allow and /usr/lib/cron/at.deny shall"
to
"The text files at.allow and at.deny, which are located in an
implementation-defined directory, shall..."
Perform similar changes for batch and crontab, noting that crontab
refers to crontab.allow and crontab.deny
|