[13:44] <hitlin37> hi, i'm doing a start my_process when there is a file change. is there any overhead if the job already running and i call start.
[13:44] <hitlin37> it says job is already running. 
[13:45] <hitlin37> i can add another condition in bash to chehck if job is running or not...or i jsutleave it like this if doesn't make any difference to send start to a job which is already running.
[15:32] <hitlin37> i think i do not understand something in upstart.
[15:33] <hitlin37> hi have a job for updating system
[15:33] <hitlin37> https://www.irccloud.com/pastebin/bV7W4oKt
[15:33] <hitlin37> since i don't have inotify bridge versiion of upstart, i'm implementating my owh mechanism
[15:34] <hitlin37> so i created another job which luaches a wifi_chehck_status script
[15:34] <hitlin37> https://www.irccloud.com/pastebin/ay7j20so
[15:35] <hitlin37> finally , in my wifi script, i chehck the status and enable if wifi is up
[15:35] <hitlin37> https://www.irccloud.com/pastebin/lOfn79W1
[15:36] <hitlin37> now, i'm keep getting from my wifi job that job terminated and respawinging.
[15:36] <hitlin37> but i dont get the reson why its terminating the wifi .sh file.
[15:36] <hitlin37> the same file runns fine from cmd line
[15:36] <hitlin37> as its inotify in while loop!
[15:51] <hitlin37> Problem is wifi job shows as "the job is terminated". but when i run the wifi_script, it works fine in blocking mode as it keeps looking at the directory using inotifywait. why would upstart terminate a while look on inotifywait? looks like i'm doing something wrong
[16:04] <hitlin37> may be i should simply my question. is there a problem if a script, called from my job calls inotiywait.