• NotAMouse (unregistered)

    Frist, snecod, TURD

  • Hmmmm (unregistered)

    Ahhhh, but this gives you errorLogFacility and logID parameters, perhaps dynamically chosen/generated! That's something you can achieve with awk in some simple ways, which should be available since they are invoking /usr/bin as a path...

  • Darren (unregistered)

    I've just been dealing with something in a similar vein. We've got an application that does a near-realtime replication of Progress data into a SQL database (to make reporting and PowerBI stuff easier).

    That application writes to a log file when it performs a sync. It also writes to another log file that that a log message about the sync was written. So we've essentially got logging about logging.

    I'm at a loss to understand the design decision that lead to someone writing log files about the success or failures of other logs files being written. It's log files all the way down.

  • SG (unregistered)

    Oh, that's nasty, because historically, running subprocesses from Java was a very expensive operation due to the cost of forking the JVM process. It's not as bad as it used to be, but I'd be very wary of that kind of thing.

  • (nodebb)

    TRWTF is catch(Exception ele). Why would anyone name their exception variable "ele", what does that even mean? !

Leave a comment on “Classic WTF: Fork and Log”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article