[Yum] logging and error logging

[seth vidal]

On Wed, 2002-06-12 at 16:47, Troy Dawson wrote:
> Michael Stenner wrote:
> > On Wed, Jun 12, 2002 at 04:22:09PM -0400, seth vidal wrote:
> > 
> >>logging will soon be like this:
> >>
> >>yum -d 0-1 == nothing, only serious errors that cause an exit
> >>yum -d 2 == standard output - just informational messages, questions,
> >>etc
> >>yum -d 3+ == debug - gratuitous output - increasing as the number
> >>increases
> >>
> >>error logs would always get printed and file (syslog-style) logs would
> >>also always occur.
> >>
> >>the -d # would only affect output and debug logs.
> > 
> > 
> > Let me see if I get this.
> > 
> > 1) -d # has no effect on what's printed to the log file
> > 2) -d # has no effect on the printing of errors (they're always
> >    printed to stdout or stderr)
> > 3) -d # only effects HOW MUCH stuff gets printed to stdout/stderr
> > 
> > Is that right?  If so, it sounds good to me.  
> > I take it the default is 2 and -d 0 is for things like cron jobs?
> > Is there a difference between 0 and 1?
> > 
> > 					-Michael
> 
> What I would like to see is the cronjob output only occurs if something was 
> updated or installed.  So what if you did
> 
> yum -d 0 == nothing, only serious errors that cause an exit
> yum -d 1 == nothing unless something happens, or serious errors that cause an exit
> 
> Beyond that, I think it looks ok.

You want the cron job to output something like:
updated : pkg pkg pkg
installed: pkg pkg pkg
erased: pkg pkg pkg


?

I had intended to put that in the log file.

It would get ugly having an output to cron if you have 100 systems
updating nightly.

-sv

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
Url : http://lists.baseurl.org/pipermail/yum/attachments/20020612/635e80dd/attachment-0001.pgp