This is a Puppet module for managing Linux consoles and terminal logins. Copyright © 2017-2020 Thomas Bellman, Linköping, Sweden. ===== LICENSING ===== This Puppet module is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This module is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this module. If not, see <http://www.gnu.org/licenses/>. ===== DEPENDENCIES ===== - nscutils Can be found at https://gitlab.liu.se/NSC/puppetmodules/nscutils.git. - cfgfile Can be found at https://gitlab.liu.se/NSC/puppetmodules/cfgfile.git. - bootloader Can be found at https://git.lysator.liu.se/bellman/puppet-bootloader.git. - systemd Can be found at https://git.lysator.liu.se/bellman/puppet-systemd.git. ===== OFFICIAL SOURCE ===== https://git.lysator.liu.se/bellman/puppet-console
Select Git revision
puppet-console
Thomas Bellman
authored
Turns out that the systemd doesn't consider the 'screensaver-disabled' service as running after the setterm command has exited, as we had it configured. We mistakenly thought it would if the service Type was "oneshot", but it doesn't, so 'systemctl status screensaver-disabled' would return 3 except during the milliseconds while setterm(1) was actually running. This causes Puppet to start it again and again every time Puppet runs. The solution to this is to set the 'RemainAfterExit' option to "yes" in the service unit file. Then systemd will consider the service to be running even if the process has exited (as long as it has run at least once). Do so.
Name | Last commit | Last update |
---|---|---|
manifests | ||
COPYING | ||
COPYING.LIB | ||
README |