Summary: | logging in portage/ebuilds | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Ken Nowack <drake_stuff> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | mholzer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://bugs.gentoo.org/show_bug.cgi?id=991 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 3585 | ||
Bug Blocks: | 2765 |
Description
Ken Nowack
2002-05-18 17:28:41 UTC
Not that I would recommend running emerge -u world from cron, it is really bad and it could hose your system as it is now maybe in the future this could become a viable something for workstations but most server admins will want to evaluate ahead of time what they're about to install. On the other hand if you do run something like that from cron the output should be emailed to root or whichever user ran the cronjob, (if you have a local mail delivery agent). /var/log/emerge.log Build output would be tremendous. see also bug #11359 <quote>Since most users will set 'emerge -u world' as a cron job for any production server</quote> I couldn't disagree more. Why would you ever do this? emerge -u world in production ? never, never, never! never touch a running system, can't figure out if it does something stupid upgrading has to be test in really production system Logging happens already. PORT_LOGDIR |