Public bug reported:

This could either be in libpam0g or libpam0g-modules, not sure.

 I have a fresh Ubuntu 14 install with the latest pam_motd. I added a cool shell
script in /etc/update-motd.d/99-coolStuff

Verified correct syntax. doing a run-parts . from that dir gave me
correct results. But the correct results didn't show up when logging in.
Eventually I figured out camel casing the file name breaks pam_motd. :(

99-coolstuff works fine from login.

Not sure if this is by design, but run-parts didn't care and I thought
this emulated the behavior of that package- at least that's what your
documentation says. Speaking of docs- there is SO much stale info about
the old update-motd package out there that it took an obnoxious amount
of time to figure out what package this was in. An update to this man
page saying it isn't done in cron and update-motd has been superseded by
this would be good.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libpam0g 1.1.8-1ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Thu Jul 24 19:45:07 2014
InstallationDate: Installed on 2014-07-24 (0 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
SourcePackage: pam
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pam (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1348455

Title:
  /etc/update-motd.d scripts fail to run if camel case

Status in “pam” package in Ubuntu:
  New

Bug description:
  This could either be in libpam0g or libpam0g-modules, not sure.

   I have a fresh Ubuntu 14 install with the latest pam_motd. I added a cool 
shell
  script in /etc/update-motd.d/99-coolStuff

  Verified correct syntax. doing a run-parts . from that dir gave me
  correct results. But the correct results didn't show up when logging
  in. Eventually I figured out camel casing the file name breaks
  pam_motd. :(

  99-coolstuff works fine from login.

  Not sure if this is by design, but run-parts didn't care and I thought
  this emulated the behavior of that package- at least that's what your
  documentation says. Speaking of docs- there is SO much stale info
  about the old update-motd package out there that it took an obnoxious
  amount of time to figure out what package this was in. An update to
  this man page saying it isn't done in cron and update-motd has been
  superseded by this would be good.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libpam0g 1.1.8-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Jul 24 19:45:07 2014
  InstallationDate: Installed on 2014-07-24 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: pam
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to