Victor Lowther b1197b3819 Have all os-refresh-config elements use su instead of sudo ... Using sudo -u to change users for a command can fail if sudo thinks it needs a controlling TTY as part of its authentication. Since this is the default config, that means that whenever the command is run in an environment that does not have a TTY (such as from init(1)), sudo will die. su does not care or check for a controlling TTY, so it will succeed as long as it is being run by root (which should be the case for all os-refresh-config elements). Therefore, instead of using sudo -u <username> -- <command> to run commands as other users, use su -s /bin/bash -c "<command>" <username> This will allow things to function in the face of a misconfigured sudo as well as allow commands to run against an account that has been locked out or has a shell that otherwise restricts what commands can be run. Change-Id: I5cc518ce42536a09e9f25c6635e191884aaaef92		2015-05-19 16:47:18 -04:00
..
configure.d	Have all os-refresh-config elements use su instead of sudo	2015-05-19 16:47:18 -04:00
post-configure.d	Run migrations from only the bootstrap host	2014-07-18 12:27:36 -07:00
pre-configure.d	Moving iptables rules to the relevant elements	2014-01-28 06:31:54 -05:00