In a previous posting, I described a specific issue I was having, with my Linux installation of Google Chrome.
I have now found a solution to this exact problem.
Chrome for Linux installs a daily cron job, which resets the file
by default. If it is absolutely necessary to override this behavior, let us say because our package manager is set up by default to pull both the 32-bit and the 64-bit contents of any repository, but the latest build of Chrome only supports a 64-bit architecture, then there is a configuration file named
This file defaults to containing
This can be
(Edit 02/06/2016 : ) Unfortunately, I have discovered that the variables defined in
Do Not change the behavior of the cron job, to rewrite the file
And so I found that slightly more aggressive editing was needed by be.
On standard Debian / Linux systems, the daily cron jobs associated with specific packages are stored in the directory
And there is a symlink in this directory, pointing to a target file, which is the script that Google Chrome runs. I did not take out the symlink. But I have changed the permission bits of the target file, to make that non-executable.