home *** CD-ROM | disk | FTP | other *** search
- READ.ME for CRON16.ZIP 20-Jan-1991
- ----------------------------------
-
- 1. NEW FEATURES
- ---------------
-
- 1.1 Escaped characters in commands
-
- Some commands require ';' characters on the command line. This is
- particularly true for utilities such as the MKS Toolkit, PolyShell or
- other UNIX environment lookalikes. When CRON sees a '\' character in
- a CRONTAB entry, it will process the next character literally even if
- it is a '!', a '~' or a ';'.
-
- Because of this, CRONTABS where commands contain path names with '\'
- characters must be converted by replacing all '\' characters with two
- backslashes, i.e.
-
- D:\DIR\SUBDIR
-
- should become
-
- D:\\DIR\\SUBDIR
-
- everywhere.
-
- This is trivially accomplished with a text editor.
-
-
- 1.2 CRONDV.EXE
-
- This is a DESQview specific version of CRON. It refuses to start outside
- DESQview. CRONDV starts programs inside DESQview in their own windows,
- just as if they were started by the Open Window option on the DESQview
- menu. See chapter 7.5 of CRON.DOC for details.
-
-
-
- 2. CHANGES IN V1.6
- ------------------
-
- 2.1 Command line options
-
- The programs that use the log file (i.e. CRON.EXE, CRONDV.EXE and
- LOGCHECK.EXE) now support two different options for locking the
- logfile.
-
- command-line option -L now attempts to lock the log file
- unconditionally. Useful with SHARE.EXE in multitasking
- environments with no network. If a locking operation fails,
- logging and verbose modes are switched off and a timestamped
- error message is written to stderr.
-
- command-line option -l (letter ell) works as -L in previous
- versions, i.e. it will only attempt to lock logfiles on a remote
- (server) machine.
-
-
- 2.2 New files in CRON16.ZIP
-
- CRONTAB.DV - this is a new sample crontab for CRONDV.EXE.
-
- READ.ME - this file.
-
- -------- End of READ.ME V1.6 ---------
-