[srslte-users] srsRAN

[Pedro Alvarez]

It's just to preserve the environment variables. In this case the
$HOME environment variable.
>From sudo's man page:

"""
    -E, --preserve-env
                Indicates to the security policy that the user wishes
to preserve their existing environment variables.  The security policy
may return
                an error if the user does not have permission to
preserve the environment.
"""

> Thanks! That clarifies everything!
Glad to help :)

Pedro

On Tue, May 11, 2021 at 4:12 PM Andrea Valori <avalori at gmail.com> wrote:
>
> Thanks! That clarifies everything!
> I did not manage to find documentation on the use of -E with sudo but works. I assume is to tell to consider which user started the command?
>
> Andrea
>
> Il giorno mar 11 mag 2021 alle 14:07 Pedro Alvarez <pedro.alvarez at softwareradiosystems.com> ha scritto:
>>
>> Hi Andrea --
>>
>> Yes this mailing list is still valid.
>>
>> Regarding the config issue, Ubuntu changed the behaviour of sudo some
>> time ago so that sudo so that the commands ran in sudo no longer have
>> access to the $HOME environment variable. That is why doing "sudo
>> srslte_install_config.sh user" will install the configs in the `/root`
>> folder.
>>
>> To avoid issues you have to do one of the following:
>> 1 - Run "srsran_install_configs.sh user" *without sudo*, and when you
>> run srsenb run "sudo -E srsenb"
>> 2 - Run "srsran_install_configs.sh user" *without sudo*, and then
>> tweak your sudoers file not to need the "sudo -E" flag.
>> 3 - Run "srsran_install_configs.sh service" and then just run "sudo
>> srsenb". This will install the configs in the "/etc/srslte" folder,
>> which does not need the "sudo -E" flag to be found.
>>
>> I personally prefer solution 3, as I don't have multiple users running
>> "srsenb" on the same machine, but different people use different
>> solutions.