ispcp.conf

[kilburn]

(12-10-2009 04:15 PM)kotso Wrote:  ispcp-omega-trunk-20091207

does ispcp locks ispcp.conf while editing?

Yes. In theory, there can only be one backend operating (modifying things) at the same time, as you can see here (lock_ system implementation). Now, it seems that either "flock()" is not working properly on your system or there's another script modifying the config file, so do you have any idea about why this may happen? I only can think of a few possible reasons:

1. You're using NFS (or another non-flock-friendly) filesystem.
2. You've made a script that modifies the apache config file by itself.
3. For some reason, you call one of the manager scripts (ispcp-*-mngr) directly, without letting ispcp-rqst-mngr do its work.

Am I right on any of these? Can you provide more info on what was running when the file got corrupted?

Thanks and sorry for the inconvenience....