Re: getty@tty1.service (was: 108 seconds to start F18 64)
On Sun, 2013-01-13 at 20:35 -0500, Felix Miata wrote: On 2013-01-07 17:04 (GMT-0700) Kevin Fenzi composed: On Mon, 07 Jan 2013 18:55:12 -0500 Felix Miata wrote: I've yet to stumble onto a reliable doc for dealing with that file, which is a symlink to /usr/lib/systemd/system/getty@.service. There is no man page for getty@.service or getty@tty1.service. I've seen bits here and there on getting tty1 to not clear, but I never manage to get it to not happen without multiple reconfiguration attempts, and reboots. 'man systemd.unit' Optionally, units may be instantiated from a template file at runtime. This allows creation of multiple units from a single configuration file. If systemd looks for a unit configuration file it will first search for the literal unit name in the filesystem. If that yields no success and the unit name contains an @ character, systemd will look for a unit template that shares the same name but with the instance string (i.e. the part between the @ character and the suffix) removed. Example: if a service getty@tty3.service is requested and no file by that name is found, systemd will look for getty@.service and instantiate a service from that configuration file if it is found. 'systemctl enable getty@tty2.service' should do the trick (and tty3, etc). Failed to issue method call: Invalid argument. :-( Try with getty@tty2.service in quotes - getty@tty2.service - at a guess, the @ is screwing up bash. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: getty@tty1.service (was: 108 seconds to start F18 64)
On 2013-01-07 17:04 (GMT-0700) Kevin Fenzi composed: On Mon, 07 Jan 2013 18:55:12 -0500 Felix Miata wrote: I've yet to stumble onto a reliable doc for dealing with that file, which is a symlink to /usr/lib/systemd/system/getty@.service. There is no man page for getty@.service or getty@tty1.service. I've seen bits here and there on getting tty1 to not clear, but I never manage to get it to not happen without multiple reconfiguration attempts, and reboots. 'man systemd.unit' Optionally, units may be instantiated from a template file at runtime. This allows creation of multiple units from a single configuration file. If systemd looks for a unit configuration file it will first search for the literal unit name in the filesystem. If that yields no success and the unit name contains an @ character, systemd will look for a unit template that shares the same name but with the instance string (i.e. the part between the @ character and the suffix) removed. Example: if a service getty@tty3.service is requested and no file by that name is found, systemd will look for getty@.service and instantiate a service from that configuration file if it is found. 'systemctl enable getty@tty2.service' should do the trick (and tty3, etc). Failed to issue method call: Invalid argument. :-( -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On Mon, 07 Jan 2013 18:07:26 -0500 Felix Miata mrma...@earthlink.net wrote: type single on the end on kernel line without quotes. To what end? Wrong post for that bit, sorry. -- Regards, Frank Still trying to learn, both old and new tricks --me . -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
108 seconds to start F18 64
Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 video=1024x768 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 /var/log/boot.log: http://fm.no-ip.com/Tmp/Linux/bootlog-f18-big41.txt What needs to be installed to capture messages from before reaching target Basic System? tty1 is cleared, and I can never remember how to prevent that, or find instructions to do so, since systemd replaced sysvinit. :-( -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/07/2013 12:28 PM, Felix Miata wrote: Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 video=1024x768 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 /var/log/boot.log: http://fm.no-ip.com/Tmp/Linux/bootlog-f18-big41.txt What needs to be installed to capture messages from before reaching target Basic System? tty1 is cleared, and I can never remember how to prevent that, or find instructions to do so, since systemd replaced sysvinit. :-( Instead you should: yum install systemd-analyze and then execute systemd-analyze blame or systemd-analyze plot bootchart.svg (probably the latter, and please post that graphic somewhere) Matthias - -- Matthias Runge mru...@matthias-runge.de mru...@fedoraproject.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ6rWxAAoJEOnz8qQwcaIW8DkH/iEFV8k+ep6f9yWPxFvAawEo r7kVOZ5+ztPYiNNYfOV9ZiVplzQfm9RjBvx1yf3/SI2g7K5t3eHTEgUBlJ3R4b6g Z0LAKhWg+494vcfQtW+oCgImTOtVEwWaWFk5QLL9lVTqHhv0j/yzqpQFvBnQofrL bL81yy9KcgnWVGY3uE7FV5Bhinfdain7DEexer69M59G09sN5JIPq5BtD2YDHDrP OS0IxFYwlqZk2KuTxQFMzAV6SkHP6WBqBKTaQC8k/DAi1HMA8Bz9X9CVt0XYhpOL GNLChuanSCtGLjCWA7T2LLzypZAFeUgpZy2JBpDE7i7U3gVEOBJ/Z/MY0P/9EWg= =FziJ -END PGP SIGNATURE- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On Mon, 07 Jan 2013 06:28:04 -0500 Felix Miata mrma...@earthlink.net wrote: Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 video=1024x768 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 In F18 KEYTABLE = KEYMAP, SYSFONT = FONT, type single on the end on kernel line without quotes. -- Regards, Frank Still trying to learn, both old and new tricks --me . -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On 2013-01-07 12:46 (GMT+0100) Matthias Runge composed: On 01/07/2013 12:28 PM, Felix Miata wrote: Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 video=1024x768 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 /var/log/boot.log: http://fm.no-ip.com/Tmp/Linux/bootlog-f18-big41.txt What needs to be installed to capture messages from before reaching target Basic System? tty1 is cleared, and I can never remember how to prevent that, or find instructions to do so, since systemd replaced sysvinit. :-( Instead you should: yum install systemd-analyze and then execute systemd-analyze blame or systemd-analyze plot bootchart.svg (probably the latter, and please post that graphic somewhere) Thanks! http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18.svg FWIW, on the 98s boot in this graphic, the occasional use eSATA device counted within the 108s was powered down. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On 2013-01-07 12:07 (GMT) Frank Murphy composed: On Mon, 07 Jan 2013 06:28:04 -0500 Felix Miata wrote: Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 video=1024x768 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 In F18 KEYTABLE = KEYMAP, SYSFONT = FONT, Done, and video=1024x768 removed. type single on the end on kernel line without quotes. To what end? -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On 2013-01-07 18:05 (GMT-0500) Felix Miata composed: On 2013-01-07 12:46 (GMT+0100) Matthias Runge composed: On 01/07/2013 12:28 PM, Felix Miata wrote: Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 video=1024x768 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 /var/log/boot.log: http://fm.no-ip.com/Tmp/Linux/bootlog-f18-big41.txt What needs to be installed to capture messages from before reaching target Basic System? tty1 is cleared, and I can never remember how to prevent that, or find instructions to do so, since systemd replaced sysvinit. :-( Instead you should: yum install systemd-analyze and then execute systemd-analyze blame or systemd-analyze plot bootchart.svg (probably the latter, and please post that graphic somewhere) Thanks! http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18.svg FWIW, on the 98s boot in this graphic, the occasional use eSATA device counted within the 108s was powered down. Another with the eSATA device powered at POST, and with clock corrected for non-working NTP (0.5s shorter): http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18b.svg Waiting on every login prompt on a tty is very annoying. Can they be configured to start at boot instead of on demand? When booting with 3 on cmdline it seems nuts that they don't. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On Mon, 2013-01-07 at 18:22 -0500, Felix Miata wrote: On 2013-01-07 18:05 (GMT-0500) Felix Miata composed: On 2013-01-07 12:46 (GMT+0100) Matthias Runge composed: On 01/07/2013 12:28 PM, Felix Miata wrote: Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 video=1024x768 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 /var/log/boot.log: http://fm.no-ip.com/Tmp/Linux/bootlog-f18-big41.txt What needs to be installed to capture messages from before reaching target Basic System? tty1 is cleared, and I can never remember how to prevent that, or find instructions to do so, since systemd replaced sysvinit. :-( Instead you should: yum install systemd-analyze and then execute systemd-analyze blame or systemd-analyze plot bootchart.svg (probably the latter, and please post that graphic somewhere) Thanks! http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18.svg FWIW, on the 98s boot in this graphic, the occasional use eSATA device counted within the 108s was powered down. Another with the eSATA device powered at POST, and with clock corrected for non-working NTP (0.5s shorter): http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18b.svg Waiting on every login prompt on a tty is very annoying. Can they be configured to start at boot instead of on demand? When booting with 3 on cmdline it seems nuts that they don't. Yes, you'd just have to adjust the systemd service config for getty@.service . But the spawning should be just about instantaneous on any reasonable config. If you have to wait for the tty to appear that sounds like a bug. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On 2013-01-07 15:28 (GMT-0800) Adam Williamson composed: On Mon, 2013-01-07 at 18:22 -0500, Felix Miata wrote: On 2013-01-07 18:05 (GMT-0500) Felix Miata composed: On 2013-01-07 12:46 (GMT+0100) Matthias Runge composed: On 01/07/2013 12:28 PM, Felix Miata wrote: Also, several seconds for login prompt to appear on each tty where not previously used on that boot. cmdline: root=LABEL=h50root13 rd.md=0 rd.lvm=0 rd.dm=0 FONT=True KEYMAP=us rd.luks=0 LANG=en_US.UTF-8 splash=verbose video=1152x864@70 3 /var/log/boot.log: http://fm.no-ip.com/Tmp/Linux/bootlog-f18-big41.txt What needs to be installed to capture messages from before reaching target Basic System? tty1 is cleared, and I can never remember how to prevent that, or find instructions to do so, since systemd replaced sysvinit. :-( Instead you should: yum install systemd-analyze and then execute systemd-analyze blame or systemd-analyze plot bootchart.svg (probably the latter, and please post that graphic somewhere) Thanks! http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18.svg FWIW, on the 98s boot in this graphic, the occasional use eSATA device counted within the 108s was powered down. Another with the eSATA device powered at POST, and with clock corrected for non-working NTP (0.5s shorter): http://fm.no-ip.com/Tmp/Linux/bootchart-big41-f18b.svg Waiting on every login prompt on a tty is very annoying. Can they be configured to start at boot instead of on demand? When booting with 3 on cmdline it seems nuts that they don't. Yes, you'd just have to adjust the systemd service config for getty@.service . I've yet to stumble onto a reliable doc for dealing with that file, which is a symlink to /usr/lib/systemd/system/getty@.service. There is no man page for getty@.service or getty@tty1.service. I've seen bits here and there on getting tty1 to not clear, but I never manage to get it to not happen without multiple reconfiguration attempts, and reboots. But the spawning should be just about instantaneous on any reasonable config. If you have to wait for the tty to appear that sounds like a bug. It happens on Cauldron too, but the delay is much longer on F18. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On Mon, 07 Jan 2013 18:55:12 -0500 Felix Miata mrma...@earthlink.net wrote: I've yet to stumble onto a reliable doc for dealing with that file, which is a symlink to /usr/lib/systemd/system/getty@.service. There is no man page for getty@.service or getty@tty1.service. I've seen bits here and there on getting tty1 to not clear, but I never manage to get it to not happen without multiple reconfiguration attempts, and reboots. 'man systemd.unit' Optionally, units may be instantiated from a template file at runtime. This allows creation of multiple units from a single configuration file. If systemd looks for a unit configuration file it will first search for the literal unit name in the filesystem. If that yields no success and the unit name contains an @ character, systemd will look for a unit template that shares the same name but with the instance string (i.e. the part between the @ character and the suffix) removed. Example: if a service getty@tty3.service is requested and no file by that name is found, systemd will look for getty@.service and instantiate a service from that configuration file if it is found. 'systemctl enable getty@tty2.service' should do the trick (and tty3, etc). kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 108 seconds to start F18 64
On Mon, 2013-01-07 at 18:55 -0500, Felix Miata wrote: Yes, you'd just have to adjust the systemd service config for getty@.service . I've yet to stumble onto a reliable doc for dealing with that file, which is a symlink to /usr/lib/systemd/system/getty@.service. There is no man page for getty@.service or getty@tty1.service. I've seen bits here and there on getting tty1 to not clear, but I never manage to get it to not happen without multiple reconfiguration attempts, and reboots. The key word is 'instantiate'. Search 'man systemd.unit' for 'instant' and you'll find some useful stuff. I don't know offhand exactly how you'd go about getting back to all-ttys-spawned-on-boot, to be honest, though, you'd want to trace all the way through how the getty@ service works first. If lennart's reading, he might pipe up. But the spawning should be just about instantaneous on any reasonable config. If you have to wait for the tty to appear that sounds like a bug. It happens on Cauldron too, but the delay is much longer on F18. So, that's the main bug here, I'd say. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
