Arch Linux

pouar

Member

Registered: 2011-11-03

Posts: 55

Website

systemd start jobs obscures VT

It's really hard to login or enter commands when systemd covers the console with "a start job is running for *". I was wondering how to stop it from covering every single VT with this. Google didn't help and I couldn't find how on the wiki"

Last edited by pouar (2014-10-31 13:47:17)

---

Yep, I'm a diaperfur now, I guess

while :;do if windows sucks;then mv windows /dev/null;pacman -Sy linux;fi;done
for i in {\ metal,core,grind};do echo death$i rules\!;done

ANOKNUSA

Member

Registered: 2010-10-22

Posts: 2,141

Re: systemd start jobs obscures VT

Can you post a screenshot? It is possible that your mundane start-up messages just aren't being cleared, but this "A startup job is running for..." message usually means some start-up process the system considers potentially vital is failing (a hanging daemon, unmounted drive or some such). That message may be a sign of a greater problem, not the problem itself.

---

Linux != Windows  ::  Ask Questions the Smart Way  ::  Configs

pouar

Member

Registered: 2011-11-03

Posts: 55

Website

Re: systemd start jobs obscures VT

Not really, it's done during bootup. What I'm hoping for is something like "systemd.show_status=true" as a boot paramater, but restrict it to a single VT rather than whatever VT you're currently running. I don't want to pass "systemd.show_status=false" because it turns these messages off entirely. The start job is updatedb.service from mlocate. It's just saying it's updating the mlocate database.

Last edited by pouar (2014-10-31 13:59:31)

---

Yep, I'm a diaperfur now, I guess

while :;do if windows sucks;then mv windows /dev/null;pacman -Sy linux;fi;done
for i in {\ metal,core,grind};do echo death$i rules\!;done

karol

Archivist

Registered: 2009-05-06

Posts: 25,440

Re: systemd start jobs obscures VT

You can check the thread about mlocate and man-db running at boot to see if you can fix it this way.