Re: Komba..

[Paul Cupis <paul@cupis.co.uk>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 23 Apr 2003 01:28, Michael Peddemors 
<michael@linuxmagic.com> wrote:
> On Tuesday 22 April 2003 15:13, Paul Cupis wrote:
> > > Because the user is no longer logged in.  The mounts mounted
> > > under their home directories are of no use to the system or any
> > > other user, until they log back in.
> >
> > What if they are still running processes which might be using those
> > mounts?
>
> Okay, how best to handle this.  If a server is running 24/7 for
> years, and users have long since been deleted, why should their
> shares still be mounted?

Deleted users if a much different scenario than users who have logged 
off and left 'long' running processes running.

> > In Microsoft Windows, AFAIK, when one logs off, all of their user
> > processes are terminated. This is not necessarily the case on
> > non-Microsoft systems. Assuming that it is the case is wrong.
>
> Well, we should be able to detect if
> 1) the user has active processes
> 2) the user is logged in (Actually that will be covered by 1)
>
> If not, the mount can be reaped.

How do you propose to reap the mounts? This is not, AFAIK, something 
which komba is concerned with.
 
Description: KDE Samba browser
 Komba2 is a GUI machine and share browser for the
 SMB protocol. Komba2 allows you to scan any number
 of subnets for machines with SMB. The workgroups,
 machines and share are shown in a tree-view.
 For each machine you can then view the list of
 shares, and mount, unmount or browse them. You can
 also search a machine by  name or ip.

If you want users to unmount things when they log off, perhaps this 
could be added as an option to komba ( [X] Always unmount upon logoff 
), but it should not be on by default. if you want unused mounts on 
your system to be unmounted, you need some daemon to do that. I am nt 
currently aware of any such daemon, though I'm sure one could be coded. 
But unmounting something accidentally or incorrectly could be 
disasterous.

> Or, at least we can make it a configuration option, so that the
> person who is installing the package can choose the behavior.

Perhaps automatic unmounting-upon-closing-komba could be added as a 
user-definable option, but I think that would be a bad idea. One should 
not have to have komba running the entire time one wants to use a share 
mounted _via_ komba. Having an unmount-upon-logoff would be better, but 
would require some part of komba to be called upon KDE logoff to do the 
unmounting.

I can understand the problem you percieve, but I do not agree with your 
proposed solutions. Users should unmount shares when they have finished 
with them. If they do not unmount them, perhaps they had a good reason 
to.

Regards,

Paul Cupis
- -- 
paul@cupis.co.uk

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+ppO+IzuKV+SHX/kRAvX8AJ9ed8vygsew7RWpRvM2jCUZ07qYQACfRn0A
iT0XM5lAofgwbHZ2odGnjAo=
=5Y4T
-----END PGP SIGNATURE-----