Assigning to dhcp, which appears to be causing it.
Please ignore/decline my nomination to fix this in Hardy: this bug is about the
regression in Jaunty. For the bug in Hardy, see bug 293000.
** Package changed: openssh (Ubuntu) => dhcp (Ubuntu)
--
openssh-server dos regression in jaunty (oom_ad
** Changed in: openssh (Ubuntu)
Status: Confirmed => Triaged
--
openssh-server dos regression in jaunty (oom_adj)
https://bugs.launchpad.net/bugs/390556
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-
I think normal users should be limited by ulimit anyway. Then this
wouldn't be a problem. See bug #182960.
--
openssh-server dos regression in jaunty (oom_adj)
https://bugs.launchpad.net/bugs/390556
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
--
openssh-server dos regression in jaunty (oom_adj)
https://bugs.launchpad.net/bugs/390556
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-serv
Confirmed this on Jaunty when configured via dhcp. karmic does not seem
to be affected.
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Importance: Low => Undecided
** Changed in: op
I have done some more investigations on the issue. I found that the
original debian patch still exists in sshd.
The problem is caused by the DHCP initialization of my network interface
during startup. The DHCP request is processed in the background while
the OpenSSH initialization script (and othe
