On 07/17/2012 03:28 PM, Freek de Kruijf wrote:

Already in openSUSE 12.1 the fam service does not work. This remains the same in 12.2. The family of courier packages depends on this service. The alternative is to use dovecot, which does not need the fam service.

Is there a bug report about fam?

So I propose to drop the family of courier and fam packages from the openSUSE distribution.

Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Jul 17, 2012 at 03:32:36PM +0200, Andreas Jaeger wrote:

On 07/17/2012 03:28 PM, Freek de Kruijf wrote:

...

Already in openSUSE 12.1 the fam service does not work. This remains the same in 12.2. The family of courier packages depends on this service. The alternative is to use dovecot, which does not need the fam service.

Is there a bug report about fam?

...

So I propose to drop the family of courier and fam packages from the openSUSE distribution.

You could use also gamin, or leave the buildrequires out of courier-imap, as it is NOT mandatory. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 07/17/2012 03:54 PM, Freek de Kruijf wrote:

On dinsdag 17 juli 2012 15:32:36 Andreas Jaeger wrote:

...

On 07/17/2012 03:28 PM, Freek de Kruijf wrote:

...

Already in openSUSE 12.1 the fam service does not work. This remains the same in 12.2. The family of courier packages depends on this service. The alternative is to use dovecot, which does not need the fam service.

Is there a bug report about fam?

...

So I propose to drop the family of courier and fam packages from the openSUSE distribution.

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... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On dinsdag 17 juli 2012 19:13:22 Robert Schweikert wrote:

On 07/17/2012 09:54 AM, Freek de Kruijf wrote:

...

On dinsdag 17 juli 2012 15:32:36 Andreas Jaeger wrote:

...

On 07/17/2012 03:28 PM, Freek de Kruijf wrote:

...

Already in openSUSE 12.1 the fam service does not work. This remains the same in 12.2. The family of courier packages depends on this service. The alternative is to use dovecot, which does not need the fam service.

Is there a bug report about fam?

...

So I propose to drop the family of courier and fam packages from the openSUSE distribution.

Sure, see https://bugzilla.novell.com/show_bug.cgi?id=719686

Well, if you refuse to start portmapper/rpcbind as suggested by coolo in comment 6 and the service needs it, I am not certain how you can reasonably expect that the service should work without it. Later (comment 11) Andreas indicates that things work just fine when portmapper is running.

You may be able to make an argument that fam should be dropped for lack of maintainer ship, but are we certain the fam maintainer knows about this bug?

Don't argue that it should be removed because it's not working when it has been shown in the bug report that indeed it does work.

I am very sorry. I completely forgot about the need to start rpcbind. In 11.4 fam starts without rpcbind. From 12.1 on it needs rpcbind and I forgot about it. Just tested it in 12.2RC1 and now fam starts when rpcbind is started. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

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

On dinsdag 17 juli 2012 22:17:17 Christian Boltz wrote:

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? ;-)

In my other message I came to the same conclusion. So two actions are suggested. The one above, the patch file is attached, and something in systemctl that gives a proper error message when fam.service is enabled while rpcbind.service is not enabled. -- fr.gr. Freek de Kruijf