Solution to the problem that aMule cannot be started in Ubuntu

AMule was not disabled when it was shut down in Ubuntu. After Ubuntu was started again, how could aMule not be started? google found a solution in mac, this method is also applicable to Ubuntu, but the file path is slightly different. After aMule is disabled abnormally, aMule cannot be started. Open Terminal and try to start it with the command line. The result is as follows, that I already have a running aMule ---------------------

AMule was not disabled when it was shut down in Ubuntu. After Ubuntu was started again, how could aMule not be started;

After google finds the solution on mac, this method also applies to Ubuntu, but the file path is slightly different;

After aMule is disabled abnormally, aMule cannot be started. Open Terminal and try to start it with the command line. The result is as follows: I already have a running aMule.

----------------------------------------------------------------------------
Initialising aMule 2.2.6 using wxGTK2 v2.8.10
Checking if there is an instance already running...
There is an instance of aMule already running
----------------------------------------------------------------------------

In some cases, the aMule is not completely closed, and the lockfile still exists. The solution is to delete the following file (the file content is actually the amule process id ):

~ /. AMule/muleLock