aMule Forum

English => en_Bugs => Topic started by: Nodsu on June 30, 2007, 11:34:17 AM

Title: Minor amuled annoyance
Post by: Nodsu on June 30, 2007, 11:34:17 AM

amuled forks to background before checking the validity of the config file.

So, in a scenario where one doesn't have EC enabled, amuled -f would happily start up, check for another running instance, fork to background and then silently exit.

Combining that with the fact that the config file usually gets lost after a system crash.. Every time I start up amuled, I have to check with top that the bloody thing actually stays running.

Title: Re: Minor amuled annoyance
Post by: skolnick on June 30, 2007, 09:56:55 PM

I guess a printf (or cout << ...whatever) when exiting would do the trick? :)