>> If you look at some of the other tests, they use awk and sed to process
>> output to strip variable components like this from the output before
I don't know how to get my hands on the output to massage it.
As an example of this, at a command prompt type:
# sleep 60 &
# kill $!
# (wait a couple of seconds then hit a return with no input)
+ Terminated sleep 60
It is the 2 shell notification messages above that are giving me problems. If
I knew how to grab them, I could massage them as needed.
So I'm hoping there is a way to either tell the test harness to ignore the fact
that it does not match.
Or that there is a way to disable the notifications.
ps, I'm using background sleeps as a timeout to make sure that the snapshot
create takes no more than 5 minutes. If the snapshot create completes
normally, then I need to kill off the sleep.
If there is no clean way to handle these shell notification messages, I can
probably figure out a different way to do it.
Deployment and Integration Specialist
Compaq ASE - Tru64 v4, v5
Compaq Master ASE - SAN Architect
The Norcross Group