* Merge from Debian unstable, remaining changes: - debian/libpam-modules.postinst: Add PATH to /etc/environment if it's not present there or in /etc/security/pam_env.conf. (should send to Debian). - debian/libpam0g.postinst: only ask questions during update-manager when there are non-default services running. - debian/patches-applied/series: Ubuntu patches are as below ... - debian/patches-applied/ubuntu-rlimit_nice_correction: Explicitly initialise RLIMIT_NICE rather than relying on the kernel limits. - Change Vcs-Bzr to point at the Ubuntu branch. - debian/patches-applied/pam_motd-legal-notice: display the contents of /etc/legal once, then set a flag in the user's homedir to prevent showing it again. - debian/update-motd.5, debian/libpam-modules.manpages: add a manpage for update-motd, with some best practices and notes of explanation. - debian/patches/update-motd-manpage-ref: add a reference in pam_motd(8) to update-motd(5)
\fIvalueN\fR\'s not mentioned explicitly\&. Note, the full list of PAM errors is available in
379
379
\FC/usr/include/security/_pam_types\&.h\F[]\&. The
380
380
\fIactionN\fR
381
can be: an unsigned integer,
382
\fIn\fR, signifying an action of \'jump over the next
383
\fIn\fR
384
modules in the stack\'; or take one of the following forms:
381
can take one of the following forms:
385
382
.PP
386
383
ignore
387
384
.RS 4
409
406
equivalent to ok with the side effect of terminating the module stack and PAM immediately returning to the application\&.
410
407
.RE
411
408
.PP
409
N (an unsigned integer)
410
.RS 4
411
equivalent to ok with the side effect of jumping over the next N modules in the stack\&. Note that N equal to 0 is not allowed (and it would be identical to ok in such case)\&.
412
.RE
413
.PP
412
414
reset
413
415
.RS 4
414
416
clear all memory of the state of the module stack and start again with the next stacked module\&.