Bug 131540

Summary:	Unable to Activate FAM
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Caesium 5 <caesium5>
Component:	Other	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P5 - None	CC:	forgotten_9r5eSHgkqj
Version:	unspecified
Target Milestone:	unspecified
Hardware:	i386
OS:	SLES 10
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

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.