I expect Christian to answer any minute with how to debug this. I'm running Sharity for several years on an older SGI,I don't know if this applies to you or not. In the past, I had to do a umount before I could restart sharity. I think it was due to the version of nfs I was running.
During this time, my work-around was to do umount -t nfs when resetting sharity. /usr/local/sharity/sbin/sharity.init stop; umount -t nfs; umount -t nfs; /usr/local/sharity/sbin/sharity.init start; Brian H. ----------------- 10/29/2002 3:38:53 PM, "Pontarelli, Brian" <[EMAIL PROTECTED]> wrote: > >Actually, the solution we have for now, which I need to put into the bug >report is this: > >1. Un-mount the Sharity file systems using the Unix umount command (not the >sharity umount command) like this: >umount -f /CIFS > >2. Find the PID for the daemon > >3. Kill this PID > >4. Restart > >For whatever reason, the Sharity daemon will not accept any requests >(dealock maybe) and therefore does not accept any system messages (I'm >guessing here). Therefore, for whatever reason, unmount the Unix mount >forcibly causes the daemon to begin accepting messages again. > >Weird. > >Thanks for the help though. > >Brian _______________________________________________ Sharity-talk mailing list [EMAIL PROTECTED] To unsubscribe see http://at.obdev.at/mailman/listinfo/sharity-talk
