% systemd-analyze blame !461
11107ms NetworkManager.service
7210ms systemd-logind.service
2897ms colord-sane.service
2845ms crond.service
1600ms cpupower.service
1565ms systemd-modules-load.service
1280ms systemd-remount-fs.service
1256ms udisks2.service
1220ms colord.service
1113ms sys-kernel-debug.mount
1112ms dev-m
I'm trying to write a service to start my network on an install without a network manager, but it seems that systemd doesn't like dhcpcd, and keeps sending it SIGTERM after it gets to a certain point.Here's the service:[Unit]
Description=Connect to NETGEAR
After=syslog.target
[Service]
Type=oneshot
ExecStart=/usr/sbin/iwconfig wlan0 essid NETGEAR key ********** ; /usr/sbin/dhcpcd w
Have a look at the man page for tmpfiles.d, I'm pretty sure that's exactly what you're looking for as far as sticking values into files in sysfs on boot. Also, in general you can stick '/bin/sh -c' in as the ExecStart to do whatever you want, including echoing things and redirecting it into files, and chain them together with a semicolon in between. For a silly
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
Can I do This start up service below, there are no errors showing once run, but the server script below does not run!
ln /lib/systemd/aquarium.service aquarium.service
systemctl daemon-reload
systemctl enable aquarium.service
systemctl start aquarium.service
thanks
aquarium.service:
[Unit]
Description=Start aquarium server
[Service]
WorkingDirectory=/home/root/python/code/aquarium/
ExecStart
please use code tags.you may want to use this service file instead:[Unit]
Description=i3lock
Before=sleep.target
[Service]
User=<user>
Type=forking
Environment=DISPLAY=:0
ExecStart=/usr/bin/i3lock -c 000000
[Install]
WantedBy=sleep.targetsystemctl enable i3lock.service
65kid
https://bbs.archlinux.org/profile.php?id=45818
2012-10-04T13:58:35Z
As suggested in the thread about the switch to systemd, I post my startup time here.
I'm trying to write a simple service file for VBoxHeadless (for my headless server).│[Unit]
Description=Virtualbox Headless WinXP VM
[Service]
ExecStart=/usr/bin/VBoxHeadless --startvm WinXP
[Install]
WantedBy=multi-user.targetSomehow whenever I run it I get (from systemctl status) the following:- % systemctl status vbo
ernestas ~ $ systemd-analyze blame 25787ms NetworkManager.service 3440ms laptop-mode-tools.service 1792ms systemd-logind.service 1573ms systemd-modules-load.service 1519ms home.mount 1305ms polkit.service 977ms systemd-udevd.service 903ms systemd-sysctl.servicWhat could be the underlying problem?