landscape-common installs a script in /etc/update-motd.d to display a banner with some basic system information.
It will not run the main landscape-sysinfo binary if the load is higher than the number of cores, see /usr/share/landscape/landscape-sysinfo.wrapper:
#!/bin/sh
cores=$(grep -c ^processor /proc/cpuinfo 2>/dev/null)
[ "$cores" -eq "0" ] && cores=1
threshold="${cores:-1}.0"
if [ $(echo "`cut -f1 -d ' ' /proc/loadavg` < $threshold" | bc) -eq 1 ]; then
echo
echo -n " System information as of "
/bin/date
echo
/usr/bin/landscape-sysinfo
else
echo
echo " System information disabled due to load higher than $threshold"
fi
Do you think it was landscape-sysinfo running that made your login take more than 60s and thus timeout?
landscape-common installs a script in /etc/update-motd.d to display a banner with some basic system information.
It will not run the main landscape-sysinfo binary if the load is higher than the number of cores, see /usr/share/ landscape/ landscape- sysinfo. wrapper:
#!/bin/sh "${cores: -1}.0" bin/landscape- sysinfo
cores=$(grep -c ^processor /proc/cpuinfo 2>/dev/null)
[ "$cores" -eq "0" ] && cores=1
threshold=
if [ $(echo "`cut -f1 -d ' ' /proc/loadavg` < $threshold" | bc) -eq 1 ]; then
echo
echo -n " System information as of "
/bin/date
echo
/usr/
else
echo
echo " System information disabled due to load higher than $threshold"
fi
Do you think it was landscape-sysinfo running that made your login take more than 60s and thus timeout?