----- Original Message -----
From: "Harry Vennik" <[EMAIL PROTECTED]>
Op zondag 2 april 2006 18:43, schreef Karol Krizka:
On 4/2/06, NoWhereMan <[EMAIL PROTECTED]> wrote:
aMSN does checks if the locked instance is already running. THe
running instance opens a random port and writes it into the lock file.
So when a new aMSN instance checks if that port is open. But if it's
not, that means the amsn crashed and the lockfile is just stale.
At least I think that's how it works.
Yeah, that's indeed what is being told all the time someone complains
about
this problem. But it seems there is a little leak in that protocol.
Sometimes
it just happens that the profile stays locked after a crash of amsn,
although
I don't know how that may happen.
really, guys I don't know, but you can do this simple test, for me it is
ALWAYS reproduceable
edit your .amsn/profiles
----cut here----
amsn_profiles_version 1
[EMAIL PROTECTED] 60742
----cut here----
for me this is ALWAYS failing, producing no output on console and just
hanging...
but if you then set it to
----cut here----
amsn_profiles_version 1
[EMAIL PROTECTED] 0
----cut here----
it will come back running...
I'm on ubuntu breezy badger and kernel 2.6.12-10-i386
bye :)
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel
