Full Disclosure mailing list archives
Re: Cronning Update Jobs
From: Max Valdez <maxvalde () fis unam mx>
Date: Sat, 27 Mar 2004 10:31:41 -0600
It would be nice for the gentoo network if you schedule that 1 every day or two, not twice a day. It's always better to see what is really going to be updated, chances are that some config file has to be modified, or a given services stops working after the update. I do a contabed emerge sync once a day, and manually update with "emerge -uDp world", and "emerge -uD world", that way I know what is going on exactly, and I can see it some package wasn't succesfully compiled, and I can manually update all others after it. Max -- Linux garaged 2.6.5-rc2-mm3 #1 Fri Mar 26 11:07:16 CST 2004 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz GenuineIntel GNU/Linux -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GS/S d- s: a-29 C++(+++) ULAHI+++ P+ L++>+++ E--- W++ N* o-- K- w++++ O- M-- V-- PS+ PE Y-- PGP++ t- 5- X+ R tv++ b+ DI+++ D- G++ e++ h+ r+ z** ------END GEEK CODE BLOCK------ gpg-key: http://garaged.homeip.net/gpg-key.txt _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Cronning Update Jobs Luke Norman (Mar 27)
- Re: Cronning Update Jobs Max Valdez (Mar 27)
- Re: Cronning Update Jobs Alexander Gretencord (Mar 27)
- RE: Cronning Update Jobs Aditya, ALD [Aditya Lalit Deshmukh] (Mar 27)
- Re: Cronning Update Jobs Nico Golde (Mar 28)
- Re: Cronning Update Jobs <- really a bad idea in Portage Tobias Weisserth (Mar 28)
- Re: Cronning Update Jobs Luke Norman (Mar 28)
- Re: Cronning Update Jobs <- really a bad idea in Portage Wesley D Craig (Mar 28)
- Re: Cronning Update Jobs Remko Lodder (Mar 28)
- Re: Cronning Update Jobs <- really a bad idea in Portage Tobias Weisserth (Mar 28)