updating files in SecureLVE

[iseletsk]

It is a bug.

[a]

yes, this file outdated ...
Ive removed it and rerun securelve_init again, then securelve_user <username>
after this hosts has been updated

is it normal behaiveiaour ?

[iseletsk]

Could you check what is in /usr/share/securelve-skeleton/etc/hosts

maybe that is the file that is not updating -- if that is the case, just copy it manually/fix it there, and re-run:
securelve_user <username>

[a]

[root@pl0 ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
10.40.95.243 pl0.srv.example.com pl0
8.8.8.8 goooooooooogle.com
::1 localhost6.localdomain6 localhost6
[root@pl0 ~]# securelve_init
/usr/share
/usr
Device /usr/share/securelve-skeleton/dev/urandom does exist already
Device /usr/share/securelve-skeleton/dev/random does exist already
Device /usr/share/securelve-skeleton/dev/tty does exist already
Device /usr/share/securelve-skeleton/dev/null does exist already
[root@pl0 ~]# securelve_user user1000
[root@pl0 ~]# su - user1000
sh-3.2$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 pl0.srv.oldhost.com pl0 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
sh-3.2$

doesn work

also it even doesn work with this command

securelve_user -u user1000 && securelve_user user1000

[iseletsk]

you will need to do securelve_init first, and then rerun: securelve_user <username> for each user
We will provide short cut in the future versions.

[a]

Howdy!
I changed main system files /etc/hosts and /etc/resolv.conf how to update this in SecureLVE container ?
securelve_update/init didn help