You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS version (cat /etc/rear/os.conf or lsb_release -a): RHEL 7
rear configuration files (cat /etc/rear/site.conf or cat /etc/rear/local.conf): n/a
Brief description of the issue: when hostname contains a dot the HOSTNAME variable in rescue mode is different then in mkrescue/mkbackop mode (within rear)
Internally, REAR defines a HOSTNAME as hostname -s, but REAR writes the uname -n to the rootfs/etc/HOSTNAME file. In recover mode the /etc/HOSTNAME file is used to define the HOSTNAME variable, which is not the same as initially.
As a result the /var/log/rear/rear-$HOSTNAME.log is not found.
The text was updated successfully, but these errors were encountered:
the scripts:
- lib/bootloader-functions.sh
- output/PXE/default/81_create_pxelinux_cfg.sh
- output/USB/Linux-i386/30_create_extlinux.sh
- rescue/GNU/Linux/95_cfg2html.sh
- rescue/default/10_hostname.sh
The 'rescue/default/10_hostname.sh' script was responsible for the hostname
mismatch in recover mode. Fix related to issue #1049
hostname
contains a dot theHOSTNAME
variable in rescue mode is different then in mkrescue/mkbackop mode (within rear)Internally, REAR defines a HOSTNAME as
hostname -s
, but REAR writes theuname -n
to therootfs/etc/HOSTNAME
file. In recover mode the/etc/HOSTNAME
file is used to define theHOSTNAME
variable, which is not the same as initially.As a result the
/var/log/rear/rear-$HOSTNAME.log
is not found.The text was updated successfully, but these errors were encountered: