title: Running npm start from ExecStart in systemctl service file
body: <p>I have the following service file:</p>
  <pre><code>[Unit]
  Description=MyApp
  After=syslog.target network.target
  StartLimitIntervalSec=0
  
  [Service]
  Type=simple
  Restart=always
  RestartSec=1
  WorkingDirectory=/opt/nodejs-sites/MyApp
  ExecStart=/usr/bin/npm start
  Environment=NODE_ENV=development
  User=root
  Group=root
  StandardOutput=syslog
  StandardError=syslog
  SyslogIdentifier=MyApp
  
  [Install]
  WantedBy=multi-user.target
  </code></pre>
  <p>Here is the error from /var/log/syslog</p>
  <pre><code>Oct 14 13:00:55 devu18 systemd[1]: Started myapp.
  Oct 14 13:00:55 devu18 systemd[3203]: myapp.service: Changing to the requested working directory failed: No such file or directory
  Oct 14 13:00:55 devu18 systemd[3203]: myapp.service: Failed at step CHDIR spawning /usr/bin/npm: No such file or directory
  Oct 14 13:00:55 devu18 systemd[1]: myapp.service: Main process exited, code=exited, status=200/CHDIR
  Oct 14 13:00:55 devu18 systemd[1]: myapp.service: Failed with result 'exit-code'.
  </code></pre>
  <p>I for the life of me can't figure out why it's complaining of cannot find the file.  npm start from the same working directory works just fine, no problems.  Am I missing some permissions or +x or something somewhere?</p>