After boot-up process systemd starts agetty, but after 1--2 seconds additional messages are appeared:
How to avoid this?
I use Arch Linux, systemd 194.
$ grep '^[^#]' /etc/systemd/system/getty.target.wants/getty@tty1.service
[Unit]
Description=Getty on %I
Documentation=man:agetty(8)
After=systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service
Before=getty.target
Ignor
Syslinux? No, that is not your boot loader, those are systemd messages about services starting. This can be avoided by modifying the Type= entry in the getty.service file to Type=idle
Trilby
https://bbs.archlinux.org/profile.php?id=54694
2013-01-23T12:20:39Z
ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty2.serviceRepeat this for remaining vts - change @tty2 to @tty3 an so on.
Šaran
https://bbs.archlinux.org/profile.php?id=51949
2012-10-04T08:28:07Z
Hi,I just got my new HP laptop and although I don't need the scanner, I'd appreciate it working I tried to extract the package you linked and it seems it consists of a sensor binary, a driver and a daemon. The first two look OK, but we'd need to rewrite the daemon to a systemd service...
Hello,After moving to systemd I have some issues regarding this new init system1. Which rc files I can delete? How can I set scheduler for my HDD like I did in rc.local?2. Is there a way to setup pure systemd on currently running system and rid off rc files?3.
WonderWoofy wrote:I guess you just need to boot into the live media and either chroot, or create the symlink manually. Remember, you are not enabling getty@.service, but rather getty@tty1.service (the .service is optional).Does adding init=/bin/bash still work? Maybe you could just do that and create the symlink.Yes it's working. What should i do next?
hi guys,i got it: https://www.archlinux.org/news/consolek … by-logind/my system worked in a initscripts/systemd mix. i already configured the DAEMONS...etc.
As far as I know the [Install] section just decides where the symlink gets put WHEN you enable, it does not automatically enable the unit. After a fresh boot, try searching for ntpd.service in /etc/systemd/system/multi-user.target.wants, which is the list which actually is enabled by you the user.
I just finished spending an hour or two in a recovery mode image generated by grub-customizer. Here's what I've found. For some reason everytime I log in Getty restarts because its holdoff time runs out. I've tried playing around with the .service file for getty, and that didn't help.