We have a server application at work that makes regular logs to a log 
file.  When the drive on which this log resides is full, the application 
stops running.  It's an app that should run if it can, so I was tasked 
with the problem of making it run when the logging drive is full.

Not a big problem, and like one of my interviewers said when I applied 
for this job, the causes were stupid little things and not from any 
grand subtleties in the code.

But of course I have to test the new version of things, which means I 
get to break the server--or, I should say, try to break the server and 
hope that I don't.

The lesson I took away from this is that C++ exceptions are like 
Pokemon:  Ya gotta catch 'em all.

Regards,
John

Post a reply to this message