This came at a perfect time for me. I'm now successfully using this method but wanted to comment that I had a horrible time debugging my daemon. It seems the log file spits out a lot of confusing errors. Sample:
*** below you find the most recent exception thrown, this will be likely (but not certainly) the exception that made the application exitabnormally ***
#
*** below you find all exception objects found in memory, some of them may have been thrown in your application, others may just be in memory because they are standard exceptions ***
#
#
#
#
The confusing part is that, at least for my env, all of those can be ignored. The more confusing part is that I couldn't figure out how to get a backtrace out of my daemon :( So I spent a good chunk of time on the errors shown in the log only to later realize they were red herrings. I ended up having to do a lot of inspecting of my daemon and finally got it working.
Anyway, it was frustrating. Hopefully the debug situation will get better? All that said, this is a great solution for the problem I had :-D So was worth the trouble.
Related posts for style mens shirts:
mini brazilian bikinis
funny vintage
embroidered t shirts in
buy jacket
underwear
See also for style mens shirts:
best men's dress shoes
the yellow band on
timmy
mens designer wallets
custom christian t shirt
No comments:
Post a Comment