We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
I will try to reproduce it and let you know.
--
stop order is wrong for nfs mounts over IPSec connections
https://bugs.launchpad.net/bugs/37536
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Is this issue still reproducible in 8.10 alpha?
** Changed in: ipsec-tools (Ubuntu)
Status: Confirmed = Incomplete
--
stop order is wrong for nfs mounts over IPSec connections
https://bugs.launchpad.net/bugs/37536
You received this bug notification because you are a member of Ubuntu
There is no valid reason to flush the SA/SP database at runlevels 0 or
6. See attached patch.
Please, apply or do something about it. This bug has been reported 10
months ago and is still in edgy, in ipsec-tools 0.6.6-1ubuntu1. I refuse
to believe Caron and I are the only ones using NFS over
Confirmed on dapper
** Changed in: ipsec-tools (Ubuntu)
Status: Unconfirmed = Confirmed
--
stop order is wrong for nfs mounts over IPSec connections
https://launchpad.net/bugs/37536
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
