Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lionel77]

Ok, first of all, the malloc messages are benign, so you don't have to worry about them.

Second, I don't think you can run the cvs version without the Terminal being open. I tried starting aMule with "amule --i-would-marry-my-mule &" to demonize it, but even then it is killed, when you close the Terminal window. I assume this is because it is not simply a command line executable, but instead a program within an app bundle.

So I would recommend just hiding Terminal (using command-h), so that it is out of your sight.

[MalAkye79]

thank you very much. i will do that.  so this CVS is a more stable version then the regular Downloadable version?  how often do you guys update amule.  its a great program by the way

[lionel77]

Well, on my machine here, pretty much any aMule version from the past 1.5 years or so runs very stable. To some extent that is because whenever aMule does crash, I post a backtrace so someone can fix the issue.


Regarding the release cycles, typically what happens is that we release a bigger new version with a lot of new features (like 2.1.0) and then a bunch of bug fixes and updates with smaller improvements (like 2.1.1-2.1.3) shortly after that. Then there is often a longer delay of like 6-9 month or so and then another bigger new version is released.

For users who want to profit from new features sooner and who are willing to run slightly more experimental versions, we offer the daily CVS sources so people can compile bleeding edge builds themselves. For Mac users we provide in addition ready-to-use CVS binaries that are updated depending on how much new code has been written in the meantime and depending on how much time I have on my hands. Usually I try to release a new CVS build every 4-6 weeks or so, but the last couple month have been a little slow, because many of the devs were busy, so that I did not see the need to release a new CVS build. I will, however, probably release the next one soon.

[MalAkye79]

you guys do a great job.   i DL both versions and i will just use whichever one gives me the best download speed.  i was told that the CVS had a bug fix for DL speed. so i will try that one untill a new Update comes out

[ken]

You should be able to use the nohup command to get aMule to keep running after the Terminal window is closed.  Something like:

Code: [Select]

nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &
It's possible that just redirecting stdout and stderr and backgrounding it would be enough, and nohup is overkill.  But no harm.

[MalAkye79]

Originally posted by ken
You should be able to use the nohup command to get aMule to keep running after the Terminal window is closed.  Something like:

Code: [Select]

nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &
It's possible that just redirecting stdout and stderr and backgrounding it would be enough, and nohup is overkill.  But no harm.

what do i type that into the terminal window?

[lionel77]

Originally posted by MalAkye79

Originally posted by ken
You should be able to use the nohup command to get aMule to keep running after the Terminal window is closed.  Something like:

Code: [Select]

nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &
It's possible that just redirecting stdout and stderr and backgrounding it would be enough, and nohup is overkill.  But no harm.

what do i type that into the terminal window?

Exactly what ken wrote above:
"nohup /Applications/aMule.app/Contents/MacOS/amule --i-would-marry-my-mule >/dev/console 2>&1 &"
(provided that your aMule application is in /Applications).