1 |
Ah, that is a good point ... assuming there's not an suid-updater |
2 |
squirreled away somewhere. I'm pretty sure that I've run firefox (lots) |
3 |
since last rebuilding it on the machine in question. |
4 |
|
5 |
Your test is good, but yields new questions: |
6 |
|
7 |
- machine 1: |
8 |
|
9 |
$ pgrep -a firefox |
10 |
*2829 /usr/lib64/firefox/firefox --name firefox -P default* |
11 |
|
12 |
$ pgrep -V |
13 |
pgrep from procps-ng 3.3.16 |
14 |
|
15 |
- machine 2 (with automatic update): |
16 |
|
17 |
$ pgrep -a firefox |
18 |
*6355 firefox* |
19 |
|
20 |
$ pgrep -V |
21 |
pgrep from procps-ng 3.3.16 |
22 |
|
23 |
In both cases, I start by just invoking "firefox" (no aliases) |
24 |
|
25 |
|
26 |
|
27 |
On 11/12/20 8:28 AM, Andreas Fink wrote: |
28 |
> On Thu, 12 Nov 2020 07:55:18 +0100 |
29 |
> n952162 <n952162@×××.de> wrote: |
30 |
> |
31 |
>> I was just informed by firefox on one of my gentoo machines that firefox |
32 |
>> has updated, I need to restart. |
33 |
>> |
34 |
>> I no longer find an option to disable automatic update. Is there no hope? |
35 |
>> |
36 |
>> And do I have to go through another 18 hour firefox emerge to get rid of |
37 |
>> their "update"? Or is their binary sitting somewhere different from |
38 |
>> "our" binary? |
39 |
>> |
40 |
>> Oh! Can I just remove their binary and do a resume-emerge? |
41 |
>> |
42 |
>> |
43 |
> When firefox is updated via emerge while it is still running, this |
44 |
> update is recognised by the running instance and it will tell you that |
45 |
> firefox was updated and needs a restart. No automatic update happened |
46 |
> as you assume, it was all done by the package manager. |
47 |
> If you insist, you can check the binary that is currently running, and |
48 |
> you will most certainly find out that it is not writeable by your user |
49 |
> account, i.e. not by the user that is running firefox: |
50 |
> pgrep -a firefox |
51 |
> |
52 |
> Cheers |
53 |
> Andreas |
54 |
> |