FS#21478 - [openssh] oom_adj is now deprecated

Attached to Project: Arch Linux
Opened by Dan McGee (toofishes) - Tuesday, 26 October 2010, 15:23 GMT
Last edited by Guillaume ALAUX (galaux) - Monday, 17 January 2011, 20:50 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Guillaume ALAUX (galaux)
Architecture All
Severity Very Low
Priority Low
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

From dmesg, now that the OOM killer changed in 2.6.36:
sshd (4218): /proc/4218/oom_adj is deprecated, please use /proc/4218/oom_score_adj instead.

Additional info:
openssh 5.6p1-1
kernel26 2.6.36-1

I'm not sure if this is in the init script or the program itself though, we may just have to wait for upstream.
This task depends upon

Closed by  Guillaume ALAUX (galaux)
Monday, 17 January 2011, 20:50 GMT
Reason for closing:  Not a bug
Comment by Dan McGee (toofishes) - Tuesday, 26 October 2010, 15:26 GMT
https://build.opensuse.org/package/view_file?file=openssh-deprecated-oom_adj.patch&package=openssh&project=Base%3ASystem&srcmd5=ed7b987d0e139bfb2f8318ce18e27e14
Comment by Thomas Bächler (brain0) - Tuesday, 26 October 2010, 17:46 GMT
We cannot add this change for now, as it will break compatibility to older kernels. I assume the deprecated interface will remain in the kernel for a few years for compatibility, so this is not a problem.

Leaving this bug open for the time being.
Comment by John (graysky) - Monday, 06 December 2010, 22:26 GMT
Thanks for the info, Dan. For those of us running kernel26, here is a modified PKGBUILD that incorporates the patch.

http://pastebin.com/QnJmAJNg
Comment by Luis García (angelblade) - Tuesday, 14 December 2010, 16:45 GMT
When the changes are effective? or how can i patch this package on my pc?
Comment by John (graysky) - Tuesday, 14 December 2010, 16:48 GMT
Dunno when effective. Usage the PKGBUILD I posted above if you wanna patch it yerself.
Comment by Dan McGee (toofishes) - Tuesday, 14 December 2010, 16:52 GMT
There is *no* need to do anything. It is a simple warning and nothing more, and the functionality will not be going away anytime soon. Just wait for upstream to address it.

Loading...