Hi, I'm confused by the listing of your crontab. Anyway, script A seems to be working ok. The problem seems to be with script B. But is this true? The snoop manpage (for Solaris 8, see http://docs.sun.com/db/doc/806-0625/6j9vfim06?q=snoop&a=view) says that "snoop requires an interactive interface". I think that means that it's supposed to be run from the command line and not from a batch script. Some other solaris commands such as truss are like that and it's hard to run them from batch scripts properly and doing that should be avoided. So maybe script A is not working exactly as expected, although the ps output shows that snoop was started. I strongly suggest switching from snoop to tcpdump which is meant to be run from batch scripts. You can get tcpdump-3.7.2 in solaris pkg format from www.sunfreeware.com.
In any case, after script A is working to your satisfaction, I suggest that you then get script B working from the command line. Then get it working from cron. It will need to run as root because snoop|tcpdump must run as root. You can test how it works from cron by scheduling it to run just a couple of minutes in the future. After that works, then set it up to run at midnight. -tristan PS: For analyzing tcpdump traces, ethereal is great and can also be obtained in pkg format from www.sunfreeware.com -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
