On 9 March 2015 at 11:52, Karel Zak <kzak@xxxxxxxxxx> wrote: > On Sun, Mar 08, 2015 at 09:02:11PM +0000, Sitsofe Wheeler wrote: >> The main issue seems to be that /etc/issue isn't reparsed when agetty >> --reload is done unless /run/agetty.reload exists before the original >> agetty is started. Is this the intended behaviour? > > No, this is a bug, fixed by commit c9f5ec0faa2b2d9cf7fc162baf99499457b8b909. > >> The second issue occurs when --autologin and --login-pause are being >> used and a reload happens even when the above is done. Since the login >> program hasn't actually been started (as we are waiting for the user >> to press enter) I expected the reload to cause agetty to reload >> /etc/issue and start waiting again but this does not currently happen. >> Is this also intentional? > > Well, it wasn't implemented, improved by commit c2ef308bbfdc9fb9a0053e258828f5bd6fbb0c5d. > > The changes will be in v2.26.1. Phew, that was fast! I've found with your patches the first issue is fixed but when waiting at the [press ENTER to login] prompt agetty --reload still has no effect... -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
