'Twas brillig, and Mark Hounschell at 09/04/12 17:40 did gyre and gimble: > On 04/09/2012 10:30 AM, Colin Guthrie wrote: >>> So I just created a test target that I expected/hoped would just start a >>> single mingetty on tty1. It did do that but I also got agettys on ttys >>> 2-6. >> >> Are you sure you get them? Are they not started on-demand as soon as you >> switch to them? This is handled by autovt@.serivce (which is just a >> symlink to getty@.service by default). >> > > You are correct, they were started "on demand" when I switched to them. > >> Systemd handles this magically. Simply set: NAutoVTs=0 in logind.conf to >> disable. >> > > Yep, that works. Can the NAutoVTs be set differently on a per target basis?
Not as far as I know, but you should be able to do something similar via a conflicts directive. e.g. if you have NAutoVTs=6 by default you can just put: Conflicts=autovt@tty1.service autovt@tty2.service ... autovt@tty6.service This should prevent then kicking in. That said, I'm really not sure how much you gain here. They are loaded on demand afterall, so it's not like they are buring CPU cycles etc. Personally it doesn't seem worth the bother to me, but maybe you have your reasons :) Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
