tmpreaper should avoid deleting Chromium's SingletonCookie / SingletonSocket

[Lei Zhang]

Please add the following files to the --protected list for Chromium / Google Chrome:
/tmp/.org.chromium.Chromium.XXXXXX/SingletonCookie
/tmp/.org.chromium.Chromium.XXXXXX/SingletonSocket
/tmp/.com.google.Chrome.XXXXXX/SingletonCookie
/tmp/.com.google.Chrome.XXXXXX/SingletonSocket

Background info:

Chromium uses a socket file so a new instance of the browser can check for an existing instance. However, if one has an AFS home dir, as reported in [1], then the socket creation would fail and Chromium would not start.

To work around this issue, Chromium creates the socket as /tmp/.org.chromium.Chromium.XXXXXX/SingletonSocket and it has a corresponding SingletonCookie in the same dir. Similarly, Google Chrome has the same setup, except the tmp directory is named /tmp/.com.google.Chrome.XXXXXX instead.

Should these files ever get deleted, say, by tmpreaper, then a new instance of Chromium would fail to see the existing running copy, and corrupt the browser profile due to two browser instances writing to the same profile data directory.

[1] http://code.google.com/p/chromium/issues/detail?id=44606,

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thiemo Nagel (tnagel)]

Note that it is not sufficient to add a protect pattern to TMPREAPER_PROTECT_EXTRA because of breakage in tmpreaper's globbing, cf. https://bugs.debian.org/789919.