I suspect you are correct, as distro (kubuntu) updates seem to have resolved the issue. On Sat, 2010-09-25 at 00:32 -0400, Dan Williams wrote: > On Mon, 2010-09-20 at 17:45 -0500, Dan Williams wrote: > > On Thu, 2010-09-09 at 09:40 -0400, Tom Sutherland wrote: > > > yes - free space is not an issue. > > > > Normally on RPM-based distros the package would create and own that > > directory, but I guess we need to create it if it doesn't exist. > > Actually, I've decided it's a disto problem. Because NM-vpnc is not > actually passing the pidfile path to vpnc, vpnc itself is determining > where to put the pidfile (and this isn't known to anything other than > vpnc itself). Thus it's not really NM's responsibility to set up the > pidfile environment for vpnc. Were NM passing an explicit pidfile path, > then it would be NM's responsibility. > > Dan > > > > Dan > > > > > On Wed, 2010-09-08 at 12:40 -0400, José Queiroz wrote: > > > > Is there free space in the FS that holds "/var/run/vpnc"? > > > > > > > > 2010/9/7 Tom Sutherland <tsuther i3businesssolutions com> > > > > From my syslog: > > > > > > > > > > > > Sep 7 13:31:07 angry-butler09 vpnc[7137]: can't open > > > > pidfile /var/run/vpnc/pid for writing > > > > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: <info> > > > > VPN connection 'WolverineECC' (IP Config Get) complete. > > > > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: <info> > > > > Policy set 'LabConn' (eth0) as default for IPv4 routing and > > > > DNS. > > > > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: <info> > > > > VPN plugin state changed: 4 > > > > Sep 7 13:31:08 angry-butler09 nm-dispatcher.action: Script > > > > '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with > > > > error status 1. > > > > Sep 7 13:37:37 angry-butler09 vpnc[7137]: select: Interrupted > > > > system call > > > > Sep 7 13:37:37 angry-butler09 vpnc[7137]: terminated by > > > > signal: 15 > > > > > > > > The tunnel interface comes up, routes are populated, but no > > > > traffic seems to flow across tunnel. > > > > > > > > If I manually create /var/run/vpnc directory prior to starting > > > > the connection, all seems to work properly. > > > > > > > > > > > > version: > > > > network-manager/maverick uptodate 0.8.1 > > > > +git.20100810t184654.ab580f4-0ubuntu2 > > > > > > > > > > > > uname -a: > > > > Linux angry-butler09 2.6.35-20-generic #29-Ubuntu SMP Fri Sep > > > > 3 14:55:28 UTC 2010 x86_64 GNU/Linux > > > > > > > > > > > > Any ideas? Is this a distro-specific thing? > > > > > > > > Regards, > > > > Tom Sutherland > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > networkmanager-list mailing list > > > > networkmanager-list gnome org > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > > > > > > > > > > > > _______________________________________________ > > > networkmanager-list mailing list > > > networkmanager-list gnome org > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > _______________________________________________ > > networkmanager-list mailing list > > networkmanager-list gnome org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > >
Attachment:
smime.p7s
Description: S/MIME cryptographic signature