Daily cron complaints after default install of sn news server.

Bug #1222 reported by Ralph Corderoy
6
Affects Status Importance Assigned to Milestone
sn (Ubuntu)
Fix Released
Medium
MOTU

Bug Description

On a fresh 5.04 install I `apt-get install sn' giving version 0.3.8-3

On a fresh 5.04 install I `apt-get install sn' giving version 0.3.8-3. Since then, I've done no further sn configuration, including adding no newsgroups. I'm receiving daily complaints from cron:

    From: Anacron <email address hidden>
    To: <email address hidden>
    Subject: Anacron job 'cron.daily' on blake
    Date: Tue, 28 Jun 2005 08:23:01 +0100 (BST)

    /etc/cron.daily/sn:
    snexpire:* is not a valid newsgroup
    run-parts: /etc/cron.daily/sn exited with return code 1

It's because /etc/cron.daily/sn does

    cd /var/spool/sn
    ...
    for f in *
    do
    ...
                        /usr/sbin/snexpire -$EXPIRETIME $f

and since /var/spool/sn is empty the `*' gets passed to snexpire.

One solution would be to

    ls |
    while read f; do
        ...
    done

instead.

Changed in sn:
assignee: nobody → motu
Revision history for this message
Ralph Corderoy (ralph-inputplus) wrote :

Setting to Confirmed; still present in sn-0.3.8-4 in Ubuntu 6.06, Dapper.

Changed in sn:
status: Unconfirmed → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

This has been fixed in 0.3.8-5, which is included already in Feisty.

Changed in sn:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.