1 |
Hmm, interesting that it shows not the full path on one machine. This |
2 |
should always show you the full path: |
3 |
for p in `pgrep firefox` ; do ls -lh /proc/${p}/exe ; done |
4 |
|
5 |
You could also check with the following command what will be executed: |
6 |
which firefox |
7 |
Use `which -a firefox` to see all possible binaries that could be found |
8 |
in $PATH. |
9 |
The default is that /usr/bin/firefox is a bash script that would start |
10 |
the real firefox binary at some point. |
11 |
|
12 |
To list all packages that are installed matching firefox you could use |
13 |
qlist -Iv firefox |
14 |
qlist is part of the app-portage/portage-utils package. |
15 |
|
16 |
Maybe that will help to see what is actually running on your system and |
17 |
where it is installed. |
18 |
|
19 |
|
20 |
|
21 |
On Thu, 12 Nov 2020 |
22 |
09:19:51 +0100 n952162 <n952162@×××.de> wrote: |
23 |
|
24 |
> Ah, that is a good point ... assuming there's not an suid-updater |
25 |
> squirreled away somewhere. I'm pretty sure that I've run firefox (lots) |
26 |
> since last rebuilding it on the machine in question. |
27 |
> |
28 |
> Your test is good, but yields new questions: |
29 |
> |
30 |
> - machine 1: |
31 |
> |
32 |
> $ pgrep -a firefox |
33 |
> *2829 /usr/lib64/firefox/firefox --name firefox -P default* |
34 |
> |
35 |
> $ pgrep -V |
36 |
> pgrep from procps-ng 3.3.16 |
37 |
> |
38 |
> - machine 2 (with automatic update): |
39 |
> |
40 |
> $ pgrep -a firefox |
41 |
> *6355 firefox* |
42 |
> |
43 |
> $ pgrep -V |
44 |
> pgrep from procps-ng 3.3.16 |
45 |
> |
46 |
> In both cases, I start by just invoking "firefox" (no aliases) |
47 |
> |
48 |
> |
49 |
> |
50 |
> On 11/12/20 8:28 AM, Andreas Fink wrote: |
51 |
> > On Thu, 12 Nov 2020 07:55:18 +0100 |
52 |
> > n952162 <n952162@×××.de> wrote: |
53 |
> > |
54 |
> >> I was just informed by firefox on one of my gentoo machines that firefox |
55 |
> >> has updated, I need to restart. |
56 |
> >> |
57 |
> >> I no longer find an option to disable automatic update. Is there no hope? |
58 |
> >> |
59 |
> >> And do I have to go through another 18 hour firefox emerge to get rid of |
60 |
> >> their "update"? Or is their binary sitting somewhere different from |
61 |
> >> "our" binary? |
62 |
> >> |
63 |
> >> Oh! Can I just remove their binary and do a resume-emerge? |
64 |
> >> |
65 |
> >> |
66 |
> > When firefox is updated via emerge while it is still running, this |
67 |
> > update is recognised by the running instance and it will tell you that |
68 |
> > firefox was updated and needs a restart. No automatic update happened |
69 |
> > as you assume, it was all done by the package manager. |
70 |
> > If you insist, you can check the binary that is currently running, and |
71 |
> > you will most certainly find out that it is not writeable by your user |
72 |
> > account, i.e. not by the user that is running firefox: |
73 |
> > pgrep -a firefox |
74 |
> > |
75 |
> > Cheers |
76 |
> > Andreas |
77 |
> > |