portsnap from cron
Hi I run a daily portsnap from cron, using the following line: /usr/sbin/portsnap cron update /dev/null 21 ; /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.1.11000.12000.13000.14000.15000.16000.17000 . done] Any idea how to get rid of it? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap from cron
Tobias Roth wrote: Hi I run a daily portsnap from cron, using the following line: /usr/sbin/portsnap cron update /dev/null 21 ; /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.1.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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap from cron
Garrett Cooper wrote: 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 Ohh, now at least I have an idea why it is suddenly happening, and how to fix it. I'll either run portsdb between portsnap and portversion, or try to grep out the unneeded stuff. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap from cron
On Sun, July 29, 2007 13:11, Tobias Roth wrote: Garrett Cooper wrote: 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 Ohh, now at least I have an idea why it is suddenly happening, and how to fix it. I'll either run portsdb between portsnap and portversion, or try to grep out the unneeded stuff. I use pkg_version. Same functionality as portversion, but its slower coz it doesn't use the INDEX.db file. Maybe you could use that to avoid the messages? :) (The speed won't matter coz its run as a cron job anyways!) Do 'pkg_version -l ' to get a list of ports that need updating . Thanks, Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
