Date: Sun, 29 Jul 2007 02:06:56 -0700 From: Garrett Cooper <youshi10@u.washington.edu> To: Tobias Roth <freebsd.lists@fsck.ch> Cc: freebsd-questions@freebsd.org Subject: Re: portsnap from cron Message-ID: <46AC58B0.6060808@u.washington.edu> In-Reply-To: <46AC527F.4010305@fsck.ch> References: <46AC527F.4010305@fsck.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46AC58B0.6060808>