[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Komba.. (More reasons why it has to reap mounts)



On Friday 25 April 2003 15:33, Paul Cupis wrote:
> > Yes, but both have to be handled.  Can you think of a basic premise
> > where if a user doesn't have a process running, he needs the mounts
> > still?
>
> Cron jobs, delayed execution of programs/scripts.

Still, default in user land should NOT be to leave these around, and hard 
mount them if they are going to need this type of behavior.

> It can unmount them - doesn't necessarily mean it should reap them.
> Perhaps you feel the same way about the other mount tools, and smbmount
> GUIs?

Yep, but the tool I am dealig with is Komba :)  Each mount tool shoudl deal 
with this issue.  Maybe a userland .kde mtab that takes precedence over 
/etc/mtab? Every KDE app at least can use the same one.

>
> Educate the users, then? They must have been educated enough to _mount_
> the shares, why not unmount them?

Hehehe  I see you don't work in the real world.. I hear this often from Linux 
Developers, but in the real world hard enough to get them to follow simple 
rules.  If they (average office user) can find a way to screw it up, assume 
they will :)

> Some special operation? Like mounting the shares? I assume you mean that
> auto-reaped shares should be the default, persistant shares should be
> an option?

Exactly... But ps, automount won't work (Don't think).. it's great for making 
a cdrom or floppy available, when you know the path .. 

-- 
--
"Catch the Magic of Linux..."
--------------------------------------------------------
Michael Peddemors - Senior Consultant
LinuxAdministration - Internet Services
NetworkServices - Programming - Security
Wizard IT Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
LinuxMagic is a Registered TradeMark of Wizard Tower TechnoServices Ltd.
--------------------------------------------------------
(604)589-0037 Beautiful British Columbia, Canada



Reply to: