On Thu, Nov 24, 2011 at 06:28:03PM +0100, Bernhard R. Link wrote: > Hi, > > I've started to write some little scripts to scan buildd logs > for some diagnostics lintian cannot do or not so easily > (planing to finally get it shown at packages.qa.debian.org's todo > item, so things get a bit more attention). > > Is there any problem with running those periodically via cron on > grieg.debian.org? It should usually not be very CPU intensive > (at most a bit IO intense for looking at the logs and then mostly > limited to new logs or new tests).
I currently don't see a problem with that. I do find it useful that log files get checked for known problems. And I can probably give you more hints on what to look for. > Also the results would need to be accessible somewhere. I guess > the easiest way would make them available via http at > buildd.debian.org/. > Could I get write access to some directory served by apache there? > > Some sample output is currently in > http://people.debian.org/~brlink/logcheck/ I've made http://buildd.debian.org/~brlink/ available for now. Maybe we should move it to a better place at some point. Kurt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
