portsnap from cron

Garrett Cooper youshi10 at u.washington.edu
Sun Jul 29 09:06:59 UTC 2007


Tobias Roth wrote:
> Hi
>
> I run a daily portsnap from cron, using the following line:
>
> /usr/sbin/portsnap cron update > /dev/null 2>&1 ;
> /usr/local/sbin/portversion -vL=
>
>
> Until recently, I only received a mail when there were ports to upgrade.
> However, now I get this every day, even when there are no new ports:
>
> [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 17465 port
> entries found
> .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000.........17000....
> ..... done]
>
>
> Any idea how to get rid of it?
>
> Thanks
>   

    That's not going to change until portversion changes. The problem is 
most likely that portsnap touches the file and portversion finds it 
necessary to update the portsdb. Processing the text from portversion 
will yield the info you want.
Cheers,
-Garrett


More information about the freebsd-questions mailing list