"Brian C. White":
> Could you write them to STDERR and the rest of the info to STDOUT?
An option to suppress them might be better.
> I thought about this, but it requries my script to know about the
> internals of crontab. If crontab ever changed, then a problem could
> arise. I prefer to keep
Steve Greenland wrote:
> > Would you mind stripping these first three lines from the "crontab -l"
> > output?
>
> Yes, because I think there is useful information there (primarily
> the second line, with the file name (usually) and date).
Could you write them to STDERR and the rest of the info to
Brian C. White wrote:
>
> Package: cron
> Version: 3.0pl1-34
>
> Running "crontab -l" has a bad habit of displaying header information
> that is not actually part of the crontab.
>
> For example:
>
> $ crontab -l -u gnats
> # DO NOT EDIT THIS FILE - edit the master and reinstall.
> # (- install
Package: cron
Version: 3.0pl1-34
Running "crontab -l" has a bad habit of displaying header information
that is not actually part of the crontab.
For example:
$ crontab -l -u gnats
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (- installed on Mon Jul 29 14:07:28 1996)
# (Cron version
4 matches
Mail list logo
