Hello, Am Dienstag, 17. Juli 2012 schrieb Andreas Jaeger:
On 07/17/2012 03:54 PM, Freek de Kruijf wrote:
Sure, see https://bugzilla.novell.com/show_bug.cgi?id=719686
Looking at the bugreport, it seems that the bug is in the init file, it needs to properly specify that the portmapper is running.
It's sad that the bug owner is ignoring this but anybody with knowledge of init scripts should be able to fix this...
I just checked this (on a server with 12.1, but that shouldn't matter too much): /etc/init.d/fam contains: # Required-Start: $remote_fs $time $named $syslog $portmap and /etc/init.d/rpcbind contains: # Provides: portmap rpcbind In other words: from my POV, the initscripts look correct - even if the dependency isn't enforced. fam doesn't seem to have a fam.service, so the initscript is still used even with systemd. The rpm dependencies also look correct - fam-server requires "portmap", which is provided by rpcbind. (As always: please correct me if my understanding of the initscript or the rpm dependencies is wrong.) To sum it up: To me, it looks like we only[tm] need a better error message that makes clear how to get famd running. The current error message famd[2572]: can't register with portmapper. should probably be extended with famd[2572]: can't register with portmapper. Please start a portmapper (for example rpcbind), then try again to start famd. Freek, this text change shouldn't be too hard - can you submit a patch, please? ;-) Regards, Christian Boltz -- Gibt es ein Buch über das maßvolle Verwenden von Fußnoten? Wenn ja, dann bin ich bereit, Dir ein Exemplar zu schicken. [Thorsten Haude zu David Haller in sl-etikette] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org