I see the following complaint when my LFS-6.8 systems starts up: pol [ /var/log ]$ dmesg | grep sshd sshd (344): /proc/344/oom_adj is deprecated, please use /proc/344/oom_score_adj instead.
I Have built OpenSSH-5.6p1 from Version svn-20110417. Seems that it has to do with this: 171 What: /proc/<pid>/oom_adj 172 When: August 2012 173 Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's 174 badness heuristic used to determine which task to kill when the kernel 175 is out of memory. 176 177 The badness heuristic has since been rewritten since the introduction of 178 this tunable such that its meaning is deprecated. The value was 179 implemented as a bitshift on a score generated by the badness() 180 function that did not have any precise units of measure. With the 181 rewrite, the score is given as a proportion of available memory to the 182 task allocating pages, so using a bitshift which grows the score 183 exponentially is, thus, impossible to tune with fine granularity. 184 185 A much more powerful interface, /proc/<pid>/oom_score_adj, was 186 introduced with the oom killer rewrite that allows users to increase or 187 decrease the badness() score linearly. This interface will replace 188 /proc/<pid>/oom_adj. 189 190 A warning will be emitted to the kernel log if an application uses this 191 deprecated interface. After it is printed once, future warnings will be 192 suppressed until the kernel is rebooted. I don't know if a newer version of openSSH already has tackled this problem. There is at first sight nothing about it on the openSSH website. pvg
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
