Bug#320584: [pkg-fetchmail-maint] Bug#320584: fetchmail startup at boot causes unnecessary error messages

Goswin von Brederlow brederlo at informatik.uni-tuebingen.de
Sat Jul 30 13:41:09 UTC 2005


Nico Golde <nion at muttng.org> writes:

> Hi,
> * Jan De Luyck <jan-bugs at kcore.org> [2005-07-30 14:04]:
>> Package: fetchmail
>> Version: 6.2.5-17
>> Severity: normal
>> 
>> Hello,
>> 
>> When fetchmail is installed, it causes spurious boot-time error messages which 
>> look worse than they are. They can be solved by first looking if /etc/fetchmailrc exists at all, and only then executing the rest of the script. Since I'm not interested in running a system-wide fetchmail, I don't have that file.
>> 
>> chown: cannot access `/etc/fetchmailrc': No such file or directory
>> run-parts: /etc/resolvconf/update-libc.d/fetchmail exited with return code 1
>> run-parts: /etc/resolvconf/update.d/libc exited with return code 1
>> 
>> /etc/fetchmailrc not found.
>> can not start fetchmail daemon...
>
> so why you are not disabling the init script of fetchmail?
> i don't think it is a bug. this message is for poeple who
> want to use the init script (normally for system wide
> fetchmails) and this doesn't work if there is no system wide
> configuration. so you have to disable it simply if you don't
> want to use this. Point me if I missed something.
> Regards Nico

I have to agree with Jan here. The /etc/init.d/fetchmail script says:

# This script will NOT start or stop fetchmail if the /etc/fetchmailrc file
# does not exist.

For me that means it also should handle this case gracefully and not
output random error messages.

MfG
        Goswin




More information about the pkg-fetchmail-maint mailing list