iwatunlock command trigger bug

mmb

I have noticed a bug in the iwatunlock command trigger.

On Solaris TSv5.5.2 , the iwatunlock command trigger reports and looks for an "Unlock" event in the /var/adm/iwevents.log

When a file is unlocked the event id that is written to the log is actually "UnLock" (capitalised L) so the iwatunlock trigger never picks up on an unlock operation.

I got around this by registering my own UnLock event trigger with iwat.

Hope that this is useful.

thanks,

- mark

johnjamesmarsh

If you are the Teamsite administrator you could always fix the iwatunlock command by editing the script. I have just done this on a development instance.