#439 Program exit when locking database

[Rob Andrews]

A suggestion: when Password Safe locks the database, I wish the program would exit (or that there was an option to do so). Perhaps I'm missing something, but since program initialization is very quick, the time/effort to restart the program and provide the safe combination is basically the same as unlocking the db from the system tray.

Since I use multiple user accounts and Fast User Switch in Windows XP, and share a psafe3 db amongst all users, currently all users but the first have to open the db as read-only.

Thanks for a great program!
Rob

[Nobody/Anonymous]

Logged In: NO

I think the unlocking of the file on the filesystem when the safe is locked is a better idea see suggestion 1853484 which would achieve what you are asking for.

[Rob Andrews]

Logged In: YES
user_id=1958002
Originator: YES

I agree that suggestion #1853484 serves the purpose as well or better.

[Julie Jones]

I'm not sure how to view suggestion 1853484.

I do want to vote for some way to force the program to exit on lock. I'm sure it is very common to store the database in a shared location and access it from multiple computers. Auto exit would fix the lock issues. It would also probably go a long way to keeping me from having multiple copies of the database that need merging.

[chris134]

+1 for this feature - we need an auto exit on lock, as people are more frequently using shared databases (either on a home network, or even on Dropbox). Automatic to avoid the dreaded "conflicted versions" that result when multiple users work on a shared version in Dropbox

[rafaelx]

I wonder what would be the users expectation if the dialog for editing an item is still open and the item's data has been modified while the auto exit event occurs. Should the data be saved silently and thus overwrite the existing one? Should the modification be discarded as long as it was not explicitly accepted by the user? Should this behaviour eventually be configurable?

Another thought. Doesn't it feel kind of wrong when applications silently disappear that the user started before?

[chris134]

@rafael-x -- good questions - I think like most things there would be a range of responses, so perhaps there could be a default behavior (e.g. what happens today) and an option to turn on the exit. Saving individual entries could be done on a copy of the entry being edited, or discarded if not saved. I think the main idea, is stop the problem with multiple users on a database, when they all need read-write at different times. In my experience, it is rare (actually never encountered) a need for two people to edit the database at the same time. However - two people editing the database over the course of a day, when one person forgets to quit - happens often.

What happens in the current model, in my experience (e.g. multiple users working in Dropbox) is an entire copy of the Password Safe database is duplicated. Which is a pain to deal with on a recurring basis, users are remote from each other, people forget the app is running when it's minimized, etc.