Mailinglist Archive: opensuse (1196 mails)

< Previous Next >
Re: [opensuse] root can't start fetchmail under SuSE 11.2
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Fri, 8 Jan 2010 00:16:21 +0100 (CET)
  • Message-id: <alpine.LSU.2.00.1001080006560.32579@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Thursday, 2010-01-07 at 22:58 +0100, Wolfgang Mueller wrote:

I recently upgraded one of my computers from 10.1 to 11.2.
Under 10.1, root was able to start the fetchmail daemon,
which read its information from /etc/fetchmailrc.

But now, under 11.2, any attempt to start the fetchmail
daemon is rejected with this message:

***************************************************************
Starting fetchmail. File /etc/fetchmailrc must be owned by you.
startproc: exit status of parent of /usr/bin/fetchmail: 6
***************************************************************

Ok, "/etc/fetchmailrc must be owned by you", i.e. by root.
As under 10.1, listing fetchmailrc gives:

*******************************************************
rw------- 1 root root 804 Jan 7 00:19 /etc/fetchmailrc
*******************************************************

But, obviously, that is not enough for getting accepted by the
new fetchmail daemon running under 11.2.

What else can I do?

Read the startup script... ;-)


Time ago, fetchmail started complaining that it should not be run by root. Thus, the chaps at Suse have modified the script so that it runs under another user.

The "/etc/init.d/fetchmail" contains:

FETCHMAIL_USER="fetchmail"

and a few more settings. I guess that the file has to be owned by that user now. It is interesting that the upgrade process didn't take care of that.

- -- Cheers,
Carlos E. R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAktGa04ACgkQtTMYHG2NR9WT0gCcD/GksfRz+ps+U4G5ndcPQv9t
SWAAn3GaifYQwemUupJy+BWTI7M0i2XT
=oB73
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
This Thread
References