[Bug 805423] Re: pam_motd performance problems

[Steve Langasek]

> We would like to have an option to run the cronjobs again.

Well, you could install a cronjob by hand, which is what you would need
to do anyway (we're not going to ship a disabled cron job in the
package).  The harder part is making pam_motd not call run-parts itself
in-line.  You could achieve that by moving /etc/update-motd.d to a
different location where pam_motd won't look for it but then you run the
risk that any new package installs that add a new update-motd.d hook
will reintroduce the problem (and, furthermore, clobber the work of your
cronjob).

So I can see a case here after all for a 'noupdate' module option that
disables the dynamic updating.

BTW, does check_by_ssh open a tty?  I believe there's another
outstanding bug about fixing pam_motd to do the update when the motd
won't actually be displayed.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/805423

Title:
  pam_motd performance problems

Status in “pam” package in Ubuntu:
  Won't Fix

Bug description:
  1) lsb_release -rd
  Description:	Ubuntu 10.04.2 LTS
  Release:	10.04

  2)  Installiert: 1.1.1-2ubuntu5.3
    Kandidat: 1.1.1-2ubuntu5.3
    Versions-Tabelle:
   *** 1.1.1-2ubuntu5.3 0
          500 http://de.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
          500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
          100 /var/lib/dpkg/status
       1.1.1-2ubuntu2 0
          500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages

  3) Login on systems with high load/a lot of io wait via ssh should
  still be possible.

  4) On servers with high load or a lot of io wait login times out,
  because pam_motd does io intensive calculations. This hurts even more
  when using nagios check_by_ssh. There should be a way to use a cron
  job again (like update-motd did). Logging into a system is more
  important than motd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/805423/+subscriptions