thanx to all who responded on my cron drama's ! I have worked around the problem. TaRT can run in daemon mode - me do that. thought it mite be easier to get the system to handle it. Thanks to Eric for his suggestion - it steered me onto the source of the problem - tart itself. -- [steve@firespeed ~]$ cat tartlog error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') error reading .TaRTrc (First time running TaRT? Try `TaRT --setup') so me 4get cron method. I guess i was thinking ( WRONGLY ) that any errors on the interpretation of the command line in crontab would have gone thru to the system log - this is not the case. u have 2 pipe it to the file as suggested. Steve "Useless Invention: Battery-operated nuclear power plants." 19:13 PM Thursday, February 22, 2001
