Bug 131540 - Unable to Activate FAM
Summary: Unable to Activate FAM
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Other (show other bugs)
Version: unspecified
Hardware: i386 SLES 10
: P5 - None : Minor (vote)
Target Milestone: unspecified
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-31 11:50 UTC by Caesium 5
Modified: 2007-10-18 13:31 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Caesium 5 2005-10-31 11:50:14 UTC 
Tried to enable the file access monitoring function under YaST and console
but got the following message under Yast:

/etc/init.d/boot.clock start returned 0 (success):
Setting up the CMOS clock..done
/etc/init.d/fam start returned 7 (program is not running):
Starting File Access Monitoring Daemon..failed

had tried it under several desktops, all same "problem".
as I am not an experience linux user, it MAY be due to my inability to tune the several home desktops :(

hope this info is useful.
Comment 1 Michael Gross 2005-10-31 16:08:28 UTC 
Hi!

Which desktop/windowmanager you're using is not of relevance for this problem.

At first, update to the latest version of SUSE Linux (10.0, final [==RC4]) and try this again. This might have already been fixed.

If it still does not work, please attach the yast2-logfiles (just to be sure) and 500 lines of your syslog (tail -500 /var/log/messages > messages.txt). Further, locate the logfile for the famd (/var/log/...) and attach it as well (I think the problem is located there, seems to crash at the startup). Thanks.
Comment 2 Michael Gross 2005-11-09 14:16:37 UTC 
If the required information can be provided, please reopen the report.