Can't tell if StartupRetroshare has completed

[public]

The web GUI needs to provide it's own UI for logging in and starting up the client proper. This requires some way to tell if RS is actually running yet but librs doesn't currently expose any race-condition proof way of doing this that I can find.

My current solution is to create my own state variable outside of librs to try and track the startup state but it would be nice if there was an in library way of doing this safely.

A mutex protected variable that gets set to something at the end of StartupRetroshare() and a function for safely reading it's state would do.

[csoler]

there's already a lock file that libretroshare puts in ~/.retroshare/[SSL id]/lock, so you can't run RS twice with the same key+location. Is is ok?

On 11/30/2011 02:53 PM, Alex Stapleton wrote:

The web GUI needs to provide it's own UI for logging in and starting up the client proper. This requires some way to tell if RS is actually running yet but librs doesn't currently expose any race-condition proof way of doing this that I can find.

My current solution is to create my own state variable outside of librs to try and track the startup state but it would be nice if there was an in library way of doing this safely.

A mutex protected variable that gets set to something at the end of StartupRetroshare() and a function for safely reading it's state would do.

---

Reply to this email directly or view it on GitHub:
#4

[public]

That seems to prevent different programs from using the same profile but doesn't prevent the same program calling StartupRetroshare() twice for some reason.

[csoler]

ah, maybe the check for the lock file is performed earlier then. The main function is main(), not StartupRetroshare()

On 12/01/2011 10:28 AM, Alex Stapleton wrote:

That seems to prevent different programs from using the same profile but doesn't prevent the same program calling StartupRetroshare() twice for some reason.

---

Reply to this email directly or view it on GitHub:
#4 (comment)