>>* I've verified that '/bin/mkdir' does exist and does run fine. So I assume
*>>* the the 'No such file or directory' refers to the target of the chdir.
*>> >>* My question is how do I troubleshoot from here? What can I do
to determine
*>>* exactly what file or directory is not being found.
I'm running systemd 215 on a fairly up-to-date Debian Jessie system.
I have a Type=forking service that fails on its first ExecStartPre command
which is using /bin/mkdir to create a directory.
The service fails to start with the following.
Apr 13 10:07:42 localhost systemd[1]: Starting OVSDB
