On 14/10/2020 11.13, Carlos E. R. wrote:
Hi:
...
Where is the problem, how do I get my name back?
Giving up. Yast, network module, hostname/dns, and I see that "hostname=localhost", so I change it there and cross my fingers. Telcontar:~ # hostname Telcontar Telcontar:~ # hostname -s Telcontar Telcontar:~ # -rw-r--r-Telcontar:~ # ls -ltr /etc/ total 5472 -rw------- 1 fetchmail root 80 Oct 7 2005 fetchmailrc ... -rw-r--r-- 1 root root 26973 Oct 14 11:06 dnsmasq.conf -rw-r--r-- 1 root root 10 Oct 14 12:07 hostname -rw-r--r-- 1 root root 1126 Oct 14 12:07 sysctl.conf Telcontar:~ # Huh? /etc/sysctl.conf? Let's check with the backup. cer@Telcontar:~> sshfs cer@Isengard:/ ~/fusermount/ cer@Telcontar:~> diff ~/fusermount/mnt/BookTelcontar/006/etc/sysctl.conf /etc/sysctl.conf cer@Telcontar:~> l ~/fusermount/mnt/BookTelcontar/006/etc/sysctl.conf /etc/sysctl.conf -rw-r--r-- 1 root root 1126 Oct 14 12:07 /etc/sysctl.conf -rw-r--r-- 1 root root 1126 Mar 22 2020 /home/cer/fusermount/mnt/BookTelcontar/006/etc/sysctl.conf cer@Telcontar:~> The file was touched, but the contents did not change - yet my computer now has the correct name. +++................ cer@Telcontar:~> cat /etc/sysctl.conf # This file is # /etc/sysctl.d/99-sysctl.conf -> /etc/sysctl.conf # CER: Check new defaults on a new system. # Disable response to broadcasts. # You don't want yourself becoming a Smurf amplifier. net.ipv4.icmp_echo_ignore_broadcasts = 1 # enable route verification on all interfaces net.ipv4.conf.all.rp_filter = 1 # disable IPv6 completely # net.ipv6.conf.all.disable_ipv6 = 1 # enable IPv6 forwarding #net.ipv6.conf.all.forwarding = 1 # increase the number of possible inotify(7) watches fs.inotify.max_user_watches = 65536 # avoid deleting secondary IPs on deleting the primary IP net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 ### converted from /etc/sysconfig/sysctl at Sun, 19 Aug 2012 01:25:29 +0200 net.ipv4.tcp_syncookies = 1 net.ipv4.ip_forward = 0 net.ipv4.tcp_ecn = 0 kernel.sysrq = 1 net.ipv6.conf.all.forwarding = 0 # http://www.zdnet.com/article/linux-tcp-flaw-lets-anyone-hijack-internet-traf... #CER 16-08-29 12:41 To: oS-en net.ipv4.tcp_challenge_ack_limit = 999999999 #CER apparently, new default. I add on 2016-10-12 net.ipv6.conf.default.use_tempaddr = 1 cer@Telcontar:~> ................++- I do again the edit to dnsmasq, but the name keeps. I check the log to see when did the name change: +++................ <3.6> 2020-10-13T00:00:01.742822+02:00 Telcontar systemd 1 - - Starting Update locate database... <3.6> 2020-10-13T00:00:01.743382+02:00 Telcontar systemd 1 - - Starting Rotate log files... <3.6> 2020-10-13T00:00:01.743955+02:00 Telcontar systemd 1 - - Starting Do daily mandb update... <3.6> 2020-10-13T00:00:01.744554+02:00 Telcontar systemd 1 - - Started Timeline of Snapper Snapshots. <3.6> 2020-10-13T00:00:01.780506+02:00 Telcontar dbus-daemon 1460 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.1408' (uid=0 pid=9288 comm="/usr/lib/snapper/systemd-he lper --timeline ") (using servicehelper) <4.5> 2020-10-13T00:00:01.788354+02:00 Telcontar su - - - (to root) root on none <3.6> 2020-10-13T00:00:01.802172+02:00 Telcontar systemd 1 - - Reloading System Logging Service. <10.6> 2020-10-13T00:00:01.802720+02:00 localhost cron 9230 - - pam_unix(crond:session): session opened for user cer by (uid=0) <9.6> 2020-10-13T00:00:01.803139+02:00 localhost CRON 9314 - - (cer) CMD (/home/cer/bin/dar_la_hora_en_cron hora) <5.6> 2020-10-13T00:00:01.803354+02:00 localhost rsyslogd - - - message repeated 17 times: [-- MARK --] <5.6> 2020-10-13T00:00:01.803562+02:00 localhost rsyslogd - - - [origin software="rsyslogd" swVersion="8.33.1" x-pid="1689" x-info="http://www.rsyslog.com"] rsyslogd was HUPed ................++- At zero hours of Tuesday - that was when syslog became aware of the name change. That afternoon I changed resolv.conf and edited dnsmasq.conf. cer@Telcontar:~> diff ~/fusermount/mnt/BookTelcontar/006/etc/resolv.conf /etc/resolv.conf No, I only wrote a 2 line comment to the file. So no idea what caused the problem... :-( -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)