From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: /etc/ipsec/user/conf overwritten?
Date: Fri, 02 Nov 2018 11:36:59 -0400 [thread overview]
Message-ID: <3d854a0c-9c74-8561-71ab-ae814f0c3652@rymes.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
I have a system on which I had included some arguments in
/etc/ipsec.user.conf, as outlined in the wiki here:
https://wiki.ipfire.org/configuration/services/ipsec/example_configuration-_roadwarrior_with_windows
I might have removed these myself, but I am fairly certain I did not,
and I looked at the file today and noticed that it was empty. My
suspicion is that a core update overwrote the file, which it shouldn't,
and I am wondering if anyone can confirm my suspicion and what can be
done to avoid that in the future if it is indeed what happened.
Any thoughts?
Tom
reply other threads:[~2018-11-02 15:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d854a0c-9c74-8561-71ab-ae814f0c3652@rymes.com \
--to=trymes@rymes.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox