Op zondag 2 april 2006 18:43, schreef Karol Krizka: > On 4/2/06, NoWhereMan <[EMAIL PROTECTED]> wrote: > > ----- Original Message ----- > > From: "Harry Vennik" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Sunday, April 02, 2006 2:28 PM > > Subject: Re: [Amsn-devel] profiles and amsn failing to start > > > > > LOL, You are saying yourself that it won't work!!!! > > > > It will work but you'll lose the ability to run more than one instance :P > > > > > The problem exists exactly because amsn is designed to be able to run > > > multiple > > > instances at once, so you can be logged in on various accounts. > > > > Well, you could then add an "allow only one instance" option with this > > fix enabled... > > Or you could write in the lock file how many istances are running and > > increase/decrease the value; also you could show the user a message like > > "The profile looks like locked by another instance of aMsn. If you are > > sure no other instances of aMsn are currently running, maybe last session > > ended unexpectedly. Force this instance to load the profile? (y/n)" > > 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.
What way is the status of the port checked? IMO best would be something like: -> PING <- PONG [EMAIL PROTECTED] (where [EMAIL PROTECTED] is a placeholder for the name of the profile that is in use by the amsn instance that is listening on the port) > > etc etc... > > > > just a thought... :) > > 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 > > -- > Cheers, > Karol Krizka > > > ------------------------------------------------------- > 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&kid0944&bid$1720&dat1642 > _______________________________________________ > Amsn-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------- 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
