| 1 |
On 2018.07.04 13:38, gevisz wrote: |
| 2 |
> 2018-07-03 16:22 GMT+03:00 Mart Raudsepp <leio@g.o>: |
| 3 |
> > Ühel kenal päeval, T, 03.07.2018 kell 14:00, kirjutas gevisz: |
| 4 |
>>> Are you, by any chance, running this command through something like |
| 5 |
>>> lxc-attach or ssh? |
| 6 |
>>>> I had the exact same problem two days ago and it turned out to be |
| 7 |
>>>> something about the environment being passed to the remote system. |
| 8 |
>>>> Sourcing /etc/profile did the trick. |
| 9 |
>>> No, I do it on my desktop staying just in front of me. So, no need |
| 10 |
>>> for ssh (and I do not know what lxc-attach is at all). |
| 11 |
> >> |
| 12 |
> >> Still, sourcing /etc/profile somehow helped: |
| 13 |
> > |
| 14 |
> > How do you obtain root privileges for the command? |
| 15 |
> |
| 16 |
> su |
| 17 |
> |
| 18 |
>> If you use su, you should be using "su -" (or "su -l" or "su |
| 19 |
>> --login"), not "su". |
| 20 |
> |
| 21 |
> I have used only "su" for already 3 years, since switched to Gentoo |
| 22 |
> from Ubuntu and never had any problems with it. |
| 23 |
> |
| 24 |
> Could you explain a little bit more why "su -" should be used instead. |
| 25 |
It's not so much needing the root environment, it's that sometimes |
| 26 |
things in your own environment cause problems if not removed when |
| 27 |
emerge runs. There is another recent thread about emerge (nodejs) |
| 28 |
failing because of sandbox violations due to some XDG variable causing |
| 29 |
an install script to try writing to somewhere it would not have it the |
| 30 |
environment had been properly sanitized. Note I consider this a |
| 31 |
general precaution, it may or may not be relevant for the subject of |
| 32 |
this thread. The problems caused by this issue are indeed infrequent |
| 33 |
and sporadic, so it's not surprising that you have not run into any of |
| 34 |
them. It seems to be related to the details in some ebuilds. |
| 35 |
|
| 36 |
> From the man page I've got the following: |
| 37 |
> |
| 38 |
> -, -l, --login |
| 39 |
> Provide an environment similar to what the user would expect |
| 40 |
> had the user logged in directly. |
| 41 |
> |
| 42 |
> But I cannot see why I need the original root environment, especially |
| 43 |
> if I never set it up. |
| 44 |
That's partly the point - the root environment is generally much more |
| 45 |
empty than that of your usual user. |
| 46 |
|
| 47 |
> > If you use sudo, you might need to pass -i (--login) option to it. |
| 48 |
> |
| 49 |
> I hate using sudo since I have been forced to use it in Ubuntu. |
| 50 |
I almost never used sudo when I used Ubuntu. I used su or logged in as |
| 51 |
root when necessary. |
| 52 |
> |
| 53 |
|
| 54 |
Jack |
Archives