> wrap this up into a regular monitor script which returns success if the > backup completes in time, and failure if it doesn't.
Nice! It works if the backup is made of a monolithic block, but that's not my case. I have different types of backup that takes place: 1) classical tar and similar (eg, Oracle exports and tar) 2) Windows 2000 backup (I haven't tested yet, but redirecting the NT event log on a Unix syslog I can control the state of the backup) 3) backup taken with tools like Oracle Enterprise Manager In some cases I have to separate the work in 3 steps: 1) send a trap "begin backup" 2) backup 3) end backup The test I took on mon, make me think as alertafter doesn't work with trap. With normal monitor it works normally. Is there a bug on alertafter+traps or is my misunderstanding of alertafter+traps behavior? Roberto T.
