On Monday 27 June 2011 11:11:59 Josef Reidinger wrote:
Dominik Heidler write:
Am 27.06.2011 10:22, schrieb Klaus Kaempf:
* Dominik Heidler
[Jun 15. 2011 14:18]: # zypper-log Reading /var/log/zypper.log ................ DONE
TIME PID VER CMD 2011-06-09 12:24 7485 1.6.9 zypper in pip 2011-06-09 12:24 7577 1.6.9 zypper in python-pip 2011-06-15 10:09 104050 1.6.9 zypper se foo 2011-06-15 10:15 104587 1.6.9 zypper se argparse 2011-06-15 11:25 112303 1.6.10 zypper rm zypper-log
Whats the value of having the pid in the output ?
You need the pid to query the corresponding logs: # zypper-log 114866
PID may also appear in the zypp/histroy indicating packages selected by the application (although this is mostly used by YaST). But as YaST and zypper logs share the same format, I'd like zypper.log to scan for this as well: genericfrontend.cc(main):668 Launched YaST2 component 'y2base' 'lan' 'ncurses' So it could also be used to process the y2logs.
sorry, but this looks confusing for me, as PID is not unique, maybe introduce a unique incrementing index number is better solution.
Maybe in addition, but not as substitute for PID. For me the PID is the main key when scanning buglogs. It usually is unique enough and if not, '-d YYYY-MM-DD PID' should help. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma@suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org