** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/719833
Title:
ssh upstart job fails to actually bring up ssh
** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719833
Title:
ssh upstart job fails to actually bring up ssh
--
ubuntu-bugs
Actually, this goes even further. All services that have the possibility
not bind to 0.0.0.0 should only be started after the last network
interface is up. I'm on a machine with 10 IP addresses and have to use
something like
start on (filesystem
and net-device-up IFACE=venet0:8)
in
Actually, this goes even further. All services that have the possibility
not bind to 0.0.0.0 should only be started after the last network
interface is up. I'm on a machine with 10 IP addresses and have to use
something like
start on (filesystem
and net-device-up IFACE=venet0:8)
in
Public bug reported:
Binary package hint: torrentflux
Passing a parameter like --bind myipaddress in the extra command line
options for BitTornado doesn't work because of the way the parameters
are passed.
Description:Ubuntu 10.04.2 LTS
Release:10.04
torrentflux:
Installed: 2.4-4
