Dear Wayde,
> Is there an archive of old sharity-talk messages? I couldn't find
> any references to one on the web page...
Sorry, but there is none. We are notoriously short of resources and none of
us has found the time to search for a software package that provides useful
mailing list archives....
> Since I'm sending a note anyways ;) What I'm looking for is any
> info on a problem that has developed lately.
>
> The platform is Solaris 2.6 on a Sun box with sharity v1.07.
> Sometime over this past weekend, sharityd died.
Can you mail me the syslog message produced during the crash? I'd like to
know which signal killed the daemon. Has anyone else seen this? I've had
reports that Sharity can die with signal 2 or 3 on Solaris. This is rather
strange because these signals are created from outside the daemon.
> When we restarted it this morning, it failed with errors to the
> effect that it couldn't remount one of the shares since it believed
> it to still be mounted.
>
> We tried to unmount all shares, and according to cifslist and df,
> they were all umount'd. But when sharity was restarted again, it
> failed believing that the share was still mounted. We have scheduled
> a reboot for tomorrow morning which I believe will clear up the
> trouble, but I'd like to hear if others have had similar problems
> and if there are any other (less drastic) solutions...
It's possible that the old mounts are still active but not in the
mount-table file. You might succeed with the system's umount commandline
tool, if you know the mount path. If it complains that the path is not
mounted, you might have to add it to the mount-table file first. This is just
a quick guess. Rebooting probably helps, too.
Regards, Christian.
--
Dipl.-Ing. Christian Starkjohann
Objective Development
mailto:[EMAIL PROTECTED] | http://www.obdev.at/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
To unsubscribe send a mail with the words "unsubscribe sharity-talk" in the
body to <[EMAIL PROTECTED]>. If you want to reach a human, please write to
<[EMAIL PROTECTED]>.
