I'm restarting this case with the timer set to 7th November 2007.
The updated spec is below and in the case dir:
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2007 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
crontab entry environment variables
1.2. Name of Document Author/Supplier:
Author: Chris Gerhard
1.3 Date of This Document:
15 October 2007
4. Technical Description
This project proposes support for and use of TZ, SHELL and HOME
variables as per crontab(4) entry varaiables, these are the only ones
that change the way cron behaves. All others can be achieved via
having the entry set the variable (SHELL is the weakest of the three to
change as it only saves on exec).
HOME solves the problems associated with NFS and cronjobs where a users
home directory is not available when the entry runs (as in the case with
secure NFS).
TZ obviously sets the time zone when the entry is valid. Allowing jobs
to run in any time zone.
The variables continue to effect all entries below them until new
entries are listed in the file. Entries would run with a HOME directory
set to the one listed and at times that are correct according to the TZ
value and with a shell specified by SHELL.
Setting any other variable results in an error when you try and save
the crontab file.
All the functionality defined in this case is exported as Committed
interfaces with a release binding of patch.
Updated man pages are in the materials directory.
All the functionality defined in this case is exported as Committed
interfaces with a release binding of patch.
Updated man pages are in the materials directory.
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
ON
6.5. ARC review type: FastTrack
6.6. ARC Exposure: open
--
Darren J Moffat
