Bug 103856 - vpnc should not provide the example file under the name of "default.conf"
Summary: vpnc should not provide the example file under the name of "default.conf"
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 1
Hardware: All All
: P5 - None : Minor
Target Milestone: ---
Assignee: Lars Müller
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-10 15:54 UTC by Jörg Mayer
Modified: 2005-08-10 23:18 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg Mayer 2005-08-10 15:54:18 UTC 
Whenever vpnc starts, it reads the file /etc/vpnc/default.conf first and after 
that it reads all other config files. Providing the example file under the 
name of default.conf will cause quite a lot of traffic to the vpn-concentrater 
given in the example file from all those users, who have not modified/added 
any config of their own but just start vpnc. 
Please fix before release.
Comment 1 Jörg Mayer 2005-08-10 16:07:02 UTC 
I forgot: naming it sample.conf would be ok
Comment 2 Lars Müller 2005-08-10 23:18:40 UTC 
I added %ghost to default.conf file which is just touched while the build
process.  This is required to keep updated vpnc installations running.

The default config file is packaged as /etc/vpnc/vpnc.conf as it is done by the
Makefile of the package.  This might better be stored at
/usr/share/doc/packages/vpnc/  I'll discuss this with the author.