288127 - kill mozilla instance on another machine when same profile is used

Status: RESOLVED WONTFIX

(Core Graveyard :: Profile: BackEnd, enhancement)

Description

[Nian Liu(n/a in a long time)]

Sometimes user has the ability to use same profile on different machine in an
intranet. However, user can't use same profile at the same time. So when user
wants to use a profile which is currentlly used on machine B on machine A,
he/she has to remote login to machine B and kill the Mozilla process manually. 

The requested feature is that when user wants to use a profile which is used on
a different machine, he/she can kill the remote Mozilla process in current
Mozilla process with an UI confirmation.

Comment 1

[Nian Liu(n/a in a long time)]

rules of thumb
1)no profile corruption
2)UI for user confirmation
3)an acceptable respond time

pls. add...

Comment 2

[Nian Liu(n/a in a long time)]

proposed solution(if user wants to use a profile on machine A and the profile is
currentlly used on machine B):

1)when user selects a profile, Mozilla process on machine A checks whether a
lock file exists and is created with a different machine(IP address). If yes,
create a suicide link which links to true. And wait a small period to time for
Mozilla proces on machine B to kill itself. This part can be done in
nsProfileLock.cpp

2)If there is no keyboard and mouse input, Mozilla process on machine B checks
whether there is a suicide link which links to true in current profile
directory. If yes, remove the link and exit. This part can be done in nsWindow.cpp.

3)Mozilla process on machine A starts up with the selected profile.

Comment 3

[R.K.Aa.]

dup of bug 134909?

Comment 4

[Nian Liu(n/a in a long time)]

(In reply to comment #3)
> dup of bug 134909?

nope. both Mozilla process starts locally on different machine. Think about your
home directory is a mount point which can be accessed from different machine.

Comment 5

[Tony Mechelynck [:tonymec]]

Profile Manager is currently unowned. Any idea if this bug is still relevant now that profile roaming has been implemented?

Comment 6

[Ben Bucksch (:BenB)]

This has nothing to do with roaming.

Comment 7

[Benjamin Smedberg]

This is not a feature I would accept. Very niche audience; very hard to test.