Package: racoon Version: 1:0.5.2-1 Severity: normal
During upgrades it would be convient if racoon was only restarted at the end of the upgrade process instead of stopped at the begining and started at the end. Currently the daemon is stopped at the very begining of the process. This can cause problems if the package cache comes in via NFS and the link to the NFS server is IPsec tunneled. The other case it causes a problem is when you are remotely logged into the computer via an ipsec tunnel and upgrade racoon. Many times it works, but if a package requires interactive debconf confiruation during the upgrade then the upgrade just hangs because the connection cut out when racoon was stopped. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages racoon depends on: ii debconf 1.4.48 Debian configuration management sy ii ipsec-tools 1:0.5.2-1 IPsec tools for Linux ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii perl 5.8.4-8 Larry Wall's Practical Extraction -- debconf information: * racoon/config_mode: direct -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
