Network services don't start automatically at boot time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openvpn (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: openvpn
On a fresh Karmic beta installation I installed openvpn but it doesn't autostart at boot. Machines upgraded from jaunty to karmic don't exhibit this issue.
ProblemType: Bug
Architecture: i386
Date: Mon Oct 12 10:06:03 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20091009)
Package: openvpn 2.1~rc19-1ubuntu1 [modified: usr/sbin/openvpn]
ProcEnviron:
LANG=de_CH.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: openvpn
Uname: Linux 2.6.31-12-generic i686
XsessionErrors:
(gnome-
(nautilus:3744): Eel-CRITICAL **: eel_preferences
(polkit-
tags: | added: regression-potential |
tags: | removed: regression-potential |
On a fresh install, no OpenVPN configuration is installed, so at boot OpenVPN would return
* Starting virtual private network daemon(s)...
* No VPN is running.
Obviously, on upgrade from jaunty, if you have configurations defined in /etc/openvpn, those would get started.
Could you give more information on the contents of /etc/openvpn on your failing "fresh beta install" and on the working "upgrade from jaunty" ?