Hi Joseph, Ya, I would agree with that, seems to make the most sense.
Is it pretty simple to write a SEG module? Could you point me to a good starting place for this? The process just needs to make the SEG-formated log file, right? So I could write it in whatever language I want? --Brian On Wed, Feb 8, 2012 at 10:49 AM, Joseph Bester <[email protected]> wrote: > > On Feb 6, 2012, at 5:22 PM, Brian O'Connor wrote: > >> I just found out from our admin that they do load the reporting log >> into a DB and Joseph indicated this would prevent SEG from running >> correctly. Does anyone have a workaround for this? Would it work to >> have another daemon periodically copy the reporting file to another >> location, appending to the file? Does anyone know the exact nature of >> why having SGE load it's reporting log into a DB would break SEG? Is >> it related to file handle closure or does it actually change the >> contents of what gets logged to the file? >> >> Thanks again for everyone's help! >> >> --Brian >> > > Probably the best way would be to have a database-aware SEG module that > can interact with the database directly to get jobevents, either through > periodic database queries or some database triggers. I'm not sure how > difficult that would be to implement, as I'm not familiar with what > the sge database interface looks like. > > Joe
