[question] How to write proper upstart script for watchman about watchman

[wez]

You shouldn't need to do this. Watchman will detach and put itself in the background when it starts up.
If you need to run it under a supervisor, you should probably use the --foreground option.

Note that the watchman model is one service per user. Launching a root-owned watchman on startup will only benefit the root user.

We use https://bitbucket.org/wez/gimli to maintain and supervise our watchman processes per user. You can enable this at compile time if you run ./configure --with-gimli

[wez]

just scrolled right to read what you're running.
Watches are persistent, so you should probably do:

/var/bi/bin/watchman watch /var/bi/var/dbf
/var/bi/bin/watchman -- trigger /var/bi/var/dbf importPr "*.DBF" "*.dbf" -- /var/bi/bicmd importPr

once to set it up, then have your upstart script be something like:

script
  exec sudo -u root /var/bi/bin/watchman --foreground
end script

[jeffreycahyono]

@wez Thanks for your helpful response. --foreground works! In my system watches are reseted on system startup. But ----statefile can fix that. Now my upstart config is like this and it worked.

description "Watchman service"

start on started beanstalkd
stop on stopping beanstalkd

script
    exec sudo -u root /var/bi/bin/watchman --statefile=/var/bi/.watchman.root.state --logfile=/var/bi/var/log/watchman.log --foreground
end script