Problem with fam update to 2.7.0-8

yogi4473 · 2006-03-14 21:38:29

First of all, this is my first post, and I wanted to mention that Arch is a really great distro and I like using it every day!

But now to my problem: the update of fam to version 2.7.0-8 changed the file /etc/rc.d/fam. Now, during startup of fam it is checked if "fam" is already running. This does not make any sense. In version 2.7.0-7 "portmap" is checked and I think, this is correct.

So I reverted "fam" to "portmap" in lines 10 and 12 of /etc/rc.d/fam and everything's running again.

Yogi

pressh · 2006-03-15 00:47:23

A bug report was filed about 10 days ago when it was in testing: http://bugs.archlinux.org/task/4108

I wonder why they moved it to current

Sander · 2006-03-17 18:49:53

Is anyone planning on fixing this? The package in current still seems to be the broken one... Thanks.

ozar · 2006-03-20 15:20:54

pressh wrote:

A bug report was filed about 10 days ago when it was in testing: http://bugs.archlinux.org/task/4108
I wonder why they moved it to current

Good question... I just installed KDE and the fam package is still broken.

Sander · 2006-03-20 17:52:38

nobody seems to care... bah.

Gullible Jones · 2006-03-20 20:51:03

ozar wrote:

pressh wrote:
A bug report was filed about 10 days ago when it was in testing: http://bugs.archlinux.org/task/4108
I wonder why they moved it to current
Good question... I just installed KDE and the fam package is still broken.

KDE can use inotify, so you don't have to have FAM running if you don't care about monitoring remote files.

pressh · 2006-03-20 22:11:42

yeah, but although it's a simple fix, change fam -> portmap in line 10 and 12 of /etc/rc.d/fam, it should be fixed, as it is annoying for everybody who's upgrading... just my $0,02

raskolnikov · 2006-03-20 23:58:15

That's easy to fix, but annonying for users... a broken package which has been reported to bugtracker should *never* go in current, especially when the fix is trivial as this one.

Gullible Jones · 2006-03-21 00:00:43

pressh wrote:

yeah, but although it's a simple fix, change fam -> portmap in line 10 and 12 of /etc/rc.d/fam, it should be fixed, as it is annoying for everybody who's upgrading... just my $0,02

Actually, I tried that and it didn't work - the rc.d script reported success, but famd did not actually start. Don't ask me why, that solution should definitely work.

pressh · 2006-03-21 09:07:48

That's strange 'cause it does work over here.
Any output when running

famd -f -d -v

as root ?

evdvelde · 2006-03-21 09:25:47

pressh wrote:

That's strange 'cause it does work over here.
Any output when running
famd -f -d -v
as root ?

The famd itself is working, it is an error in the initscript...

pressh · 2006-03-21 09:37:06

evdvelde wrote:

pressh wrote:
That's strange 'cause it does work over here.
Any output when running
famd -f -d -v
as root ?
The famd itself is working, it is an error in the initscript...

Gullible Jones wrote:

pressh wrote:
yeah, but although it's a simple fix, change fam -> portmap in line 10 and 12 of /etc/rc.d/fam, it should be fixed, as it is annoying for everybody who's upgrading... just my $0,02

Actually, I tried that and it didn't work - the rc.d script reported success, but famd did not actually start. Don't ask me why, that solution should definitely work.

Please read edvelde

pressh · 2006-03-22 08:32:31

although it might work, it is not correct!!!
Portmap is needed for fam to run, so it chould check in line 8 of your code above, if portmap is running or not.
so line 8-11 would be

if [ ! -f /var/run/daemons/portmap ]; then
       stat_fail
       echo "ERROR: portmap is not running"
       exit 1

for people who are lazy to click on the bug report above

Gullible Jones · 2006-03-22 21:07:37

Is portmap needed for FAM to function at all, or is it needed only for monitoring remote files?

pressh · 2006-03-22 23:25:09

On the fam website (http://oss.sgi.com/projects/fam/) they say portmap is needed for fam to function at all.

Loke · 2006-03-24 21:14:12

Thanks for temp fix However hopefully, it'll be fixed soon.

raskolnikov · 2006-03-24 22:16:02

For those who are using testing, you can replace fam with gamin. I run Gnome 2.14 from testing with gamin, with no problem at all (and you can remove portmap if you don't need it, too)

Gullible Jones · 2006-03-24 22:25:05

Gamin doesn't monitor remote files though, and is unmaintained... At any rate, if you don't need to monitor remote files, you probably don't have to install or run anything extra - a lot of apps are using inotify to monitor local files, so gamin is no longer necessary.

ozar · 2006-03-25 22:08:26

Just noticed that 2.7.0-9 is in the Arch repo now. Has anyone tried it and verified that it fixes the problem that is the subject of this thread?

pressh · 2006-03-25 22:53:52

ozar wrote:

Just noticed that 2.7.0-9 is in the Arch repo now. Has anyone tried it and verified that it fixes the problem that is the subject of this thread?

Haven't tried yet, but looking at the daemons script in cvs atm, and the problem has been fixed.

Gullible Jones · 2006-03-25 22:59:22

It works, and the rc.d script starts portmap first as well; however, it does not stop portmap when turning off. Here goes another bug report.

raskolnikov · 2006-03-25 23:02:15

Where do you have seen gamin is unmaintened ?
I thought it was developped to be a Gnome replacement of fam :?

JGC · 2006-03-25 23:49:28

gamin is useless. It was developed to make use of inotify and to get rid of a daemon running as root. Nowadays, both KDE and GNOME utilize native inotify, so using fam/gamin is deprecated. Since gamin does exactly do the same as gnome-vfs and kdelibs can do, it's useless now. When switching to gamin, the thing you loose is network monitoring. gamin doesn't work on NFS for example, where fam does. Gnome picked this up by using inotify for local filesystems and fam for remote (NFS) filesystems.

Gullible Jones · 2006-03-26 00:25:16

Since everything now seems to use FAM and/or inotify, perhaps gamin should just be removed from Testing?

raskolnikov · 2006-03-26 12:04:13

If a fam implementation is not valuable when using only local files, I think I can remove it but gnome-vfs depends on it, and many packages require gnome-vfs :?

Arch Linux

#1 2006-03-14 21:38:29

Problem with fam update to 2.7.0-8

#2 2006-03-15 00:47:23

Re: Problem with fam update to 2.7.0-8

#3 2006-03-17 18:49:53

Re: Problem with fam update to 2.7.0-8

#4 2006-03-20 15:20:54

Re: Problem with fam update to 2.7.0-8

#5 2006-03-20 17:52:38

Re: Problem with fam update to 2.7.0-8

#6 2006-03-20 20:51:03

Re: Problem with fam update to 2.7.0-8

#7 2006-03-20 22:11:42

Re: Problem with fam update to 2.7.0-8

#8 2006-03-20 23:58:15

Re: Problem with fam update to 2.7.0-8

#9 2006-03-21 00:00:43

Re: Problem with fam update to 2.7.0-8

#10 2006-03-21 09:07:48

Re: Problem with fam update to 2.7.0-8

#11 2006-03-21 09:25:47

Re: Problem with fam update to 2.7.0-8

#12 2006-03-21 09:37:06

Re: Problem with fam update to 2.7.0-8

#13 2006-03-22 08:32:31

Re: Problem with fam update to 2.7.0-8

#14 2006-03-22 21:07:37

Re: Problem with fam update to 2.7.0-8

#15 2006-03-22 23:25:09

Re: Problem with fam update to 2.7.0-8

#16 2006-03-24 21:14:12

Re: Problem with fam update to 2.7.0-8

#17 2006-03-24 22:16:02

Re: Problem with fam update to 2.7.0-8

#18 2006-03-24 22:25:05

Re: Problem with fam update to 2.7.0-8

#19 2006-03-25 22:08:26

Re: Problem with fam update to 2.7.0-8

#20 2006-03-25 22:53:52

Re: Problem with fam update to 2.7.0-8

#21 2006-03-25 22:59:22

Re: Problem with fam update to 2.7.0-8

#22 2006-03-25 23:02:15

Re: Problem with fam update to 2.7.0-8

#23 2006-03-25 23:49:28

Re: Problem with fam update to 2.7.0-8

#24 2006-03-26 00:25:16

Re: Problem with fam update to 2.7.0-8

#25 2006-03-26 12:04:13

Re: Problem with fam update to 2.7.0-8

Board footer