[SOLVED]start a service *AFTER another one has executed completely

Question

How can i make "test.service" to start after "customstartup.service" has been fully executed?
As you can see, even if test.service Requires customstartup and customstartup.service is "oneshot", test.service is started while customstartup is still starting!
The following is in a linux container:
[root@archiso ~]# cat /etc/systemd/system/customstartup.service
[Unit]
Description=customstartup
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/sleep 100
[Install]
WantedBy=multi-user.target
[root@archiso ~]# cat /etc/systemd/system/test.service
[Unit]
Description=test
Requires=customstartup.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/sh -c "echo hi all"
[Install]
WantedBy=multi-user.target
# systemctl status customstartup
● customstartup.service - customstartup
Loaded: loaded (/etc/systemd/system/customstartup.service; enabled)
Active: activating (start) since gio 2014-07-03 16:30:10 CEST; 12s ago
Main PID: 32 (sleep)
CGroup: /machine.slice/machine-root\x2dimage.scope/system.slice/customstartup.service
└─32 /usr/bin/sleep 100
[root@archiso ~]# systemctl status test
● test.service - test
Loaded: loaded (/etc/systemd/system/test.service; enabled)
Active: active (exited) since gio 2014-07-03 16:30:10 CEST; 23s ago
Process: 26 ExecStart=/usr/bin/sh -c echo hi all (code=exited, status=0/SUCCESS)
Main PID: 26 (code=exited, status=0/SUCCESS)
CGroup: /machine.slice/machine-root\x2dimage.scope/system.slice/test.service
lug 03 16:30:10 archiso sh[26]: hi all
lug 03 16:30:10 archiso systemd[1]: Started test.
Any hints? Is there a way to enforce the wait?
Thanks.
Last edited by kokoko3k (2014-07-03 15:59:37)

Answer 1

From systemd.unit:
Requires=
           Configures requirement dependencies on other units. If this unit gets activated, the
           units listed here will be activated as well. If one of the other units gets
           deactivated or its activation fails, this unit will be deactivated. This option may be
           specified more than once or multiple space-separated units may be specified in one
           option in which case requirement dependencies for all listed names will be created.
           Note that requirement dependencies do not influence the order in which services are
           started or stopped. This has to be configured independently with the After= or Before=
           options. If a unit foo.service requires a unit bar.service as configured with
           Requires= and no ordering is configured with After= or Before=, then both units will
           be started simultaneously and without any delay between them if foo.service is
           activated. Often it is a better choice to use Wants= instead of Requires= in order to
           achieve a system that is more robust when dealing with failing services.