An interrupted pkgadd session left stale locks that prevented to run the
Thanks to those who spent valuable saturday time to answer:
Casper Dik <casper@holland.Sun.COM>
email@example.com (Sanjay Patel)
Ric Anderson <firstname.lastname@example.org>
The suggestions were to look for the lock in
and clear it
or run pkgadd under truss, for example with
truss -f -t open -t stat pkgadd xxx
in place of
The last opened or stated file could be the lock.
I have not been able to test them yet, however Im sure the truss procedure
will show the cause -- as it always does --.
I should have thought that before!
-- Oscar Goldes
-- ORDEN Argentina SA
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:47 CDT