Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a network appliance box serving as an end point for several site to site IPsec VPN tunnels. raccon's docs specify that a log file can be written to with the -l option. My clunky approach to segregate log info into tunnel specific files is just to spawn multiple raccon processes on boot with the -f and -l option set for each specifying the particular tunnel config and log output.

Before I try that out on production, does anyone have a clean and neat log structure for individual IPsec tunnels? I can parse the main log file for textual identifying strings, but I deem that a sub-optimal solution.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.