| 1 |
On 21/01/2019 20:25, Jacques Montier wrote: |
| 2 |
> Le lun. 21 janv. 2019 à 19:04, Nikos Chantziaras <realnc@×××××.com |
| 3 |
> <mailto:realnc@×××××.com>> a écrit : |
| 4 |
> |
| 5 |
> I can't see why "emerge -uv bash" would ever invoke sudo. So I'd say |
| 6 |
> that you should first find out what command is being executed with |
| 7 |
> sudo. |
| 8 |
> To do that, try to emerge bash, and when the sudo prompt pops up, |
| 9 |
> switch |
| 10 |
> to another terminal window and do: |
| 11 |
> |
| 12 |
> ps aux | grep sudo |
| 13 |
> |
| 14 |
> What's the output of that? |
| 15 |
> |
| 16 |
> ps aux | grep sudo |
| 17 |
> 267:root 19845 0.0 0.0 54260 4304 pts/0 S+ 19:23 0:00 |
| 18 |
> sudo eix-update |
| 19 |
|
| 20 |
Well, something is trying to execute a "sudo eix-update". The bash |
| 21 |
ebuild certainly doesn't, so you should check your installation for any |
| 22 |
weird scripts or aliases you might be using. A grep on /etc for |
| 23 |
"eix-update" might also reveal something: |
| 24 |
|
| 25 |
grep -r eix-update /etc |
| 26 |
|
| 27 |
And also check your env and aliases: |
| 28 |
|
| 29 |
which emerge |
| 30 |
alias | grep emerge |
| 31 |
env | grep eix |
| 32 |
|
| 33 |
These are general hints on where to look, since I have no clue myself as |
| 34 |
to why an "emerge -uv bash" would ever try and execute "sudo |
| 35 |
eix-update", so it seems you have digging to do. |
Archives