[network-manager-openswan/dcbw/avesh-fixes: 6/10] Fixed an issue where writing configuration on stdin should not end with \n as it gives error. It use

[Dan Williams <dcbw src gnome org>]

commit e2aa41b86012963328d59550d7b82a19f1f79d2f
Author: Avesh Agarwal <avagarwa redhat com>
Date:   Tue Dec 10 14:05:06 2013 -0500

    Fixed an issue where writing configuration on stdin should not end with \n as it gives error. It used to 
work previously, but not with latest versions.

 src/nm-openswan-service.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/src/nm-openswan-service.c b/src/nm-openswan-service.c
index ec0553c..f9bea3d 100644
--- a/src/nm-openswan-service.c
+++ b/src/nm-openswan-service.c
@@ -577,7 +577,8 @@ nm_openswan_config_write (gint openswan_fd, NMSettingVPN *s_vpn,
 
         write_config_option (fdtmp1, " nm_configured=yes\n");
         //write_config_option (fdtmp1, " leftupdown=%s\n", NM_OSW_UPDOWN_PATH);
-        write_config_option (fdtmp1, " auto=add\n");
+        //write_config_option (fdtmp1, " auto=add\n");
+        write_config_option (fdtmp1, " auto=add");
         //write_config_option (fdtmp1, " #connectionname=%s\n", nm_setting_vpn_get_data_item (s_vpn, 
NM_SETTING_VPN_SETTING_NAME));
         //write_config_option (fdtmp1, " #connectionname=%s\n", nm_setting_vpn_get_data_item (s_vpn, 
NM_SETTING_NAME));
        }