LOL, You are saying yourself that it won't work!!!! 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.
Harry Op zondag 2 april 2006 14:01, schreef NoWhereMan: > A small thought about that annoying problem of > amsn-failing-to-start-on-locked-port , so here's my (almost stupid) idea :) > > init process begins: > - aMsn creates a ~/.amsn/amsn.lock file. : aMsn is open. > > aMsn quits: > - aMsn deletes the file > > Next amsn start: > init process: > if the file is not deleted aMsn knows something went wrong during the last > session, so it resets the locks in the ~/.amsn/profiles file > > I know this would avoid running two aMsn instances at once, but could solve > this annoyng problem... well... > > 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 ------------------------------------------------------- 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
