Bug 105153 - change fam heuristics in YaST
Summary: change fam heuristics in YaST
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-17 12:09 UTC by Stanislav Brabec
Modified: 2005-08-18 15:44 UTC (History)
6 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Brabec 2005-08-17 12:09:13 UTC
I have just submitted gnome-vfs2 change and it does not require fam daemon
running for local file systems. It should imply heuristic change.

Current state:

If user selects GNOME, fam is started by default.

Proposed state and proposed texts:

Do not start FAM by default.

Add following question to NFS (SMB, AFS,...) clients, if GNOME or KDE is installed:

Do you want to turn on remote file alteration monitor (FAM) support?
Please note that it will only work, if server supports it, too.

Add following question to NFS (SMB, AFS,...) clients:
To support file alteration monitor (FAM) on your clients, you need to
install/start fam daemon. Do you want to start it by default?

Note: Opening FAM ports on firewall may be required. Please consult it with
Adrian, he can say more about it.
Comment 1 Arvin Schnell 2005-08-17 12:26:09 UTC
Very late, we have feature and text freeze.
Comment 2 Martin Vidner 2005-08-17 12:43:06 UTC
The question is likely only to confuse users. 
What is FAM good for? Why turn it on? Why not turn it on? 
Why should the heuristic change anyway? The dist meeting minutes do not say 
why 
(http://mailman.suse.de/mlarch//SuSE/results/2005/results.2005.08/msg00014.html). 
Comment 3 Klaus Kämpf 2005-08-17 12:55:43 UTC
-> aj, adrian  
Comment 4 Stanislav Brabec 2005-08-17 13:04:08 UTC
Original heuristic was needed for GNOME, which was not able to notify local file
changes without running fam. Now it will select gamin in this case, so running
fam by default is not needed.

But for network notification it is.

You may want to rephrase it:

FAM is File Alteration Monitor. It allows to notify desktop environment on file
changes. It is especially useful for home-over-NFS environment, less useful for
nearly static data exported from somewhere.

Why not to run it? - If you don't want to support notify or in case of paranoid
security requirements.

Why this dialog is useful? Because admin can not know the connection about lack
of change notification on desktops and running fam on both server and desktop.
Comment 5 Andreas Jaeger 2005-08-17 13:41:29 UTC
We can disable starting of fam now also for Gnome.

We should not mix a Gnome workaround with an administrator feature. If we want 
it as this, it should become not dependend on Gnome. So this is the wrong 
place. 

Sorry, we cannot make this change anymore in YaST.  Please make a feature
request for 10.1 instead.
Comment 6 Jiri Srain 2005-08-17 13:57:06 UTC
OK, also I will modify the control file in order not to touch sysconfig/fam at  
all (we modified the FAM_LOCAL_ONLY variable there) and not to start it by  
default at all.  
  
What about netdaemon? It is the same trash in YaST code, desktop-specific  
daemon (for GNOME) which needs to run with root permissions...  
Comment 7 Marcus Meissner 2005-08-17 14:10:53 UTC
i guess netdaemon behaviour cannot be changed right now., 
Comment 8 Andreas Jaeger 2005-08-17 14:27:24 UTC
Leave netdaemon.
Comment 9 Jiri Srain 2005-08-18 15:44:06 UTC
OK, just not touching FAM configuration at all. control file submitted.