Tool reports: TFW068 (S) A severe problem occurred while read locking the "/usr2/mmarion/cadence/tbdata/locks/globalData_itself" file. The system reason for this message is >>No locks available<<. Read locking has failed. TFW068 Oct 12 19:02:49 preto061 kernel: lockd/statd: failed to create /var/lib/nfs/sm/192.168.94.17: err=-13 Oct 12 19:02:49 preto061 kernel: lockd: failed to monitor 192.168.94.17 Lockd is running, I've verified this. Cadence says it's a suse thing, that Redhat works fine. Anyone seen this error and know a fix? Only hit I got on google was to another suse list that said make sure lockd is running.. which I've done. Oddly, I can't stop and restart lockd either. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Steven: "Are you ok?" Scott: "Yeah... it's just been a stressful week." Steven: "Yeah, and it's Tuesday morning." -- Boston Public