Kostya M
Kostya M
this folder already force for 1 eye. but maybe you have another eye under other user.
after adding, you have two processes with same pids (1567): ``` 5ba80f973d1f9235ef940bc4 detector ...................... up (14:14, 7%, 64Mb, ) 5bfc56a23d1f922e4a7a8046 detector ...................... up (14:14, 7%, 64Mb, ) ``` so maybe...
are you use `daemonize: true`?
looks like impossible, btw, you can see all what happens in eye log.
this line is ok, eye find that file was changed outside. try also restart eye.
i not sure how properly use it with rvm, easiest add it to bunder and use as `bundle exec eye`
check_identity should disable this, i not see in code anything else. are you sure that config loaded and process have this option? (eye x -c) btw, why process change pid_file?
yes, i finded, this is not related to check_identity, this just how managed pid_file with `daemonize true`, need to think what to do here, maybe add another option: `trust_pid_file_change true`
HOME not required for root user, but for custom user HOME should be.
technically it possible, it would just get current process stdout, stderr, and call `tail | grep` on it.