Am Dienstag, 23. September 2003 18:46 schrieb Stroller: > > I feel unhappy with automatic system updates. Should etc-update be > > executed > > automatically after the emerge or not? Should every operator check > > his/her > > computer every morning to see if en etc-update gives something to do? > > The `emerge --update` is done separately - no-one sensible would advise > system updates without manual intervention. However if all the files > are stored on one machine & exported over NFS, then it is expedient to > have that machine do the fetching of all files. A cron job to `emerge > sync && emerge -fud world` does NO installation or upgrading of any > systems - it only updates the local portage database & fetches the > updates you require. It would, I would think, be quite easy to unshare > the NFS export before getting the files, and reshare it afterwards, as > part of the cron job. If this is done at 4am, then it is likely to > cause little interruption to service in most environments.
Besides I share your opinion, that shell-scripting is an adequate way of cleaning distfiles, I must admit, that a cron-job, which calls emerge sync && emerge -fud world only makes sense on a shared .../distfiles, if and only if all machines sharing this, have the same packages installed. Given I have a server w/o X and such and some desktop machines naturally with this things. The share resides on the server, because this is the only machine 24/7 up. How could an update of X, KDE etc happen and use already downloaded files? When the desktops call emerge -ud world parallel, wouldn't that cause problems? Am I missing something? I'd love to do it this way, but I found no workaround for this problem yet. > Stroller. > -- > [EMAIL PROTECTED] mailing list Michael -- [EMAIL PROTECTED] mailing list
