Re: [PATCH] gnome-vfs: Don't monitor read-only filesystems
- From: "Manuel Amador (Rudd-O)" <amadorm usm edu ec>
- To: George Farris <george gmsys com>
- Cc: Alexander Larsson <alexl redhat com>, Nautilus <nautilus-list gnome org>
- Subject: Re: [PATCH] gnome-vfs: Don't monitor read-only filesystems
- Date: Fri, 16 Apr 2004 19:48:28 -0400
A temporary solution would be to disable FAM in /etc/xinetd.d (just drop a
disable = yes line in the fam config, then service reload xinetd).
Both nautilus and konqueror should revert to polling. Unless you have a
thousand NFS clients, that won't be a problem at all.
Quoting George Farris <george gmsys com>:
> On Fri, 2004-04-09 at 12:30, Alexander Larsson wrote:
> > On Sat, 2004-04-10 at 07:12, George Farris wrote:
> > > On Thu, 2004-04-08 at 10:50, Manuel Amador (Rudd-O) wrote:
> > > > > > No, killing fam was enough.. Fam was maintaining an open fd on the
> cdrom
> > > > > > drive. Killing it allows unmounting the drive.
> > > > >
> > > > > Killing fam was enough? Thats like saying "its not an app fault,
> killing
> > >
> > > Except that is is seriously unthinkable to ask a user to reboot their
> > > station every time they want to unmount their CD-ROM. We are all
> > > wanting GNOME "to just work" and then something screwy like fam gets
> > > mixed in. Bah! I've been migrating users over to Linux for ages and
> > > it's these little things that completely turn them off. So, yes,
> > > killing fam and telling it to never start again is the right thing to
> > > do, until it gets fixed.
> > >
> > > And yes I know how to get the cd to unmount without rebooting but no
> > > newbie and I mean NO newbie will easily figure it out.
> >
> > Of course its bad that we hang the cdrom unmount and we're working on
> > fixing that, but I'm completely confused by what your mail is about. Do
> > you think its easier to tell users to su to root and kill fam than
> > killing the user process that is actually causing fam to lock the
> > unmount? Thats what my mail was about...
>
> Sorry Alexander, maybe I wasn't clear, it was late last night when I
> posted:-( I'm just not clear on why it would be difficult to ignore the
> /dev/cdrom devices in fam.
>
> What is difficult is telling users coming from Windows how to find,
> understand and kill the process when they've never had to do something
> like that before. It's completely alien to them. Anyway I'm not
> helping get it fixed and should shut up. I was merely pointing out that
> fam should probably never have been released with this issue. It has
> caused many phone calls with "how do I eject my *&&*%&$%^$ cd" and all
> sorts of email on various mailing lists.
>
> We have to fight so many issues migrating users that these types of
> issues should be a no brainer.
>
> Cheers
>
> --
> George Farris <george gmsys com>
>
> --
> nautilus-list mailing list
> nautilus-list gnome org
> http://mail.gnome.org/mailman/listinfo/nautilus-list
>
suerte,
Rudd-O
===========================================================
UNIVERSIDAD TECNICA FEDERICO SANTA MARIA
CAMPUS GUAYAQUIL
CENTRO DE SERVICIOS INFORMATICOS
Mail enviado a traves de IMP-USM: http://www.usm.edu.ec/imp
Los invitamos a visitar http://www.usm.edu.ec
===========================================================
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]