missing manpage for limits.conf

Bug #21556 reported by asdf
6
Affects Status Importance Assigned to Milestone
pam (Debian)
Fix Released
Unknown
pam (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I cannot find the manpage for limits.conf on my ubuntu sys (breezy), on my
debian sarge box it exists. Here are the related packages i installed. I'm not
sure if other manpages are missing too.

< root@nx7010:~ [0] # dpkg -l | grep manpages | awk '{print $2}'
manpages
manpages-dev
manpages-posix
manpages-posix-dev

Thx for your time in advance.

CVE References

Revision history for this message
asdf (asdf123123-deactivatedaccount-deactivatedaccount) wrote :

I cannot find the manpage for limits.conf on my ubuntu sys (breezy), on my
debian sarge box it exists. Here are the related packages i installed. I'm not
sure if other manpages are missing too.

< root@nx7010:~ [0] # dpkg -l | grep manpages | awk '{print $2}'
manpages
manpages-dev
manpages-posix
manpages-posix-dev

Thx for your time in advance.

Revision history for this message
Tollef Fog Heen (tfheen) wrote :

It has been removed on purpose:

shadow (1:4.0.3-36) unstable; urgency=low
[...]
    - Remove limits.5 and limits.conf.5 man pages which do not
      reflect the way we deal with limits in Debian
      Closes: #288106, #244754
[...]
 -- Christian Perrier <email address hidden> Mon, 20 Jun 2005 23:37:56 +0300

So it's a bug that it's in Debian too.

Revision history for this message
asdf (asdf123123-deactivatedaccount-deactivatedaccount) wrote :

Thx for reacting so fast. I read the debian bugs about this issue: As far as i
understand the problem is that some information in this manpage is simply not
correct or outdated, so they simply removed this solution. However I think
solving this issue should be to fix this manpage and not remove it ..

(to debian: I just checked my sarge box, which still has it. I think debian
removed it after the sarge release)

Revision history for this message
asdf (asdf123123-deactivatedaccount-deactivatedaccount) wrote :

Created an attachment (id=3789)
draft for a new manpage

I made a quick draft for a new manpage for limits.conf, by just copying the
comments from the default file..

Revision history for this message
In , Nicolas François (nicolas-francois) wrote : severity of 382660 is wishlist, merging 313486 382660

# Automatically generated email from bts, devscripts version 2.9.20
severity 382660 wishlist
merge 313486 382660

Revision history for this message
Rich Johnson (nixternal) wrote :

It has been over a year since the last activity concerning this issue. Has this issue been resolved?

In the mean time, I am going to close this bug report due to inactivity and length of time. If you feel this is still an issue, I insist that you go right ahead and reopen this report. Thank you!

Changed in pam:
status: Unconfirmed → Rejected
Revision history for this message
Dennis Kaarsemaker (dennis) wrote :

Inactivity is not a good reason to close a bug, unless the inactivity is because input from the reporter is needed.

Changed in pam:
status: Rejected → Unconfirmed
Changed in pam:
status: Unknown → Unconfirmed
Revision history for this message
Bastian (bastian-absoluterend) wrote :

I wanted to read this manpage when I tried to figure out why setting nofiles limits do not have any effect. I too consider this missing manpage a bug.

Revision history for this message
Alessio Igor Bogani (abogani) wrote :

Still present in Edgy and in Feisty Beta

Changed in pam:
status: Unconfirmed → Confirmed
Tollef Fog Heen (tfheen)
Changed in pam:
assignee: tfheen → nobody
Revision history for this message
Louis Acresti (louis.acresti) wrote :

Still present in Feisty; are the default comments in the limits.conf file even correct? (See Nils' draft above)

Revision history for this message
In , Steve Langasek (vorlon) wrote : tagging 313486, tagging 300773, tagging 330545, tagging 184270

# Automatically generated email from bts, devscripts version 2.10.6
tags 313486 pending
tags 300773 pending
tags 330545 pending
tags 184270 pending

Changed in pam:
status: New → Fix Committed
Revision history for this message
In , Steve Langasek (vorlon) wrote : Bug#313486: fixed in pam 0.99.7.1-2
Download full text (12.8 KiB)

Source: pam
Source-Version: 0.99.7.1-2

We believe that the bug you reported is fixed in the latest version of
pam, which is due to be installed in the Debian FTP archive:

libpam-cracklib_0.99.7.1-2_amd64.deb
  to pool/main/p/pam/libpam-cracklib_0.99.7.1-2_amd64.deb
libpam-cracklib_0.99.7.1-2_i386.deb
  to pool/main/p/pam/libpam-cracklib_0.99.7.1-2_i386.deb
libpam-doc_0.99.7.1-2_all.deb
  to pool/main/p/pam/libpam-doc_0.99.7.1-2_all.deb
libpam-modules_0.99.7.1-2_amd64.deb
  to pool/main/p/pam/libpam-modules_0.99.7.1-2_amd64.deb
libpam-modules_0.99.7.1-2_i386.deb
  to pool/main/p/pam/libpam-modules_0.99.7.1-2_i386.deb
libpam-runtime_0.99.7.1-2_all.deb
  to pool/main/p/pam/libpam-runtime_0.99.7.1-2_all.deb
libpam0g-dev_0.99.7.1-2_amd64.deb
  to pool/main/p/pam/libpam0g-dev_0.99.7.1-2_amd64.deb
libpam0g-dev_0.99.7.1-2_i386.deb
  to pool/main/p/pam/libpam0g-dev_0.99.7.1-2_i386.deb
libpam0g_0.99.7.1-2_amd64.deb
  to pool/main/p/pam/libpam0g_0.99.7.1-2_amd64.deb
libpam0g_0.99.7.1-2_i386.deb
  to pool/main/p/pam/libpam0g_0.99.7.1-2_i386.deb
pam_0.99.7.1-2.diff.gz
  to pool/main/p/pam/pam_0.99.7.1-2.diff.gz
pam_0.99.7.1-2.dsc
  to pool/main/p/pam/pam_0.99.7.1-2.dsc

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek <email address hidden> (supplier of updated pam package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 26 Aug 2007 19:15:09 -0700
Source: pam
Binary: libpam0g-dev libpam0g libpam-modules libpam-doc libpam-runtime libpam-cracklib
Architecture: source amd64 all i386
Version: 0.99.7.1-2
Distribution: unstable
Urgency: low
Maintainer: Steve Langasek <email address hidden>
Changed-By: Steve Langasek <email address hidden>
Description:
 libpam-doc - Documentation of PAM
 libpam-runtime - Runtime support for the PAM library
 libpam-cracklib - PAM module to enable cracklib support
 libpam-modules - Pluggable Authentication Modules for PAM
 libpam0g - Pluggable Authentication Modules library
 libpam0g-dev - Development files for PAM
Closes: 62193 119689 127931 165067 178225 181451 184270 212165 220157 241661 300773 305058 313486 328084 330545 331208 333141 336344 350620 354309 360460 362855 368100 411812 412484 416665 436005 436222 439038 439040
Changes:
 pam (0.99.7.1-2) unstable; urgency=low
 .
   * New upstream release; thanks to Roger Leigh and Jan Christoph Nordholz
     for their extensive work in helping to prepare for this update in Debian.
     Closes: #360460.
     - now uses autoconf for library detection, so SELinux should not be
       unconditionally enabled on non-Linux archs. Closes: #333141.
     - pam_mail notice handling has been completely reworked, so there should
       no longer be missing spaces in the messages. Closes: #119689.
     -...

Changed in pam:
status: Fix Committed → Fix Released
Revision history for this message
In , Debbugs Internal Request (owner-bugs) wrote : Internal Control

# A New Hope
# A log time ago, in a galaxy far, far away
# something happened.
#
# Magically this resulted in the following
# action being taken, but this fake control
# message doesn't tell you why it happened
#
# The action:
# Bug archived.
thanks
# This fakemail brought to you by your local debbugs
# administrator

Revision history for this message
Steve Langasek (vorlon) wrote :

Fixed in gutsy, which includes Linux-PAM 0.99.7.1.

Changed in pam:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.