head	1.2;
access;
symbols
	morgan_0_75:1.1.1.2
	pam_unpruned:1.1.1.1
	morgan_0_65:1.1.1.1
	MORGAN:1.1.1;
locks; strict;
comment	@# @;


1.2
date	98.11.25.19.46.08;	author jdp;	state dead;
branches;
next	1.1;

1.1
date	98.11.18.01.16.21;	author jdp;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	98.11.18.01.16.21;	author jdp;	state Exp;
branches;
next	1.1.1.2;

1.1.1.2
date	2001.05.03.09.36.07;	author markm;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Remove files that we don't use and are unlikely to use.  You can
still get them with "cvs upd -r pam_unpruned" if you want to look at
them.
@
text
@$Id: README,v 1.3 1997/01/04 20:42:43 morgan Exp $

This is a help file for the pam_time module. It explains the need for
pam_time and also the syntax of the /etc/security/time.conf file.
[a lot of the syntax is freely adapted from the porttime file of the
shadow suite.]

1. Introduction
===============

It is desirable to restrict access to a system and or specific
applications at various times of the day and on specific days or over
various terminal lines.

The pam_time module is intended to offer a configurable module that
satisfies this purpose, within the context of Linux-PAM.

2. the /etc/security/time.conf file
===================================

This file is the configuration script for defining time/port access
control to the system/applications.

Its syntax is described in the sample ./time.conf provided in this
directory.

unrecognised rules are ignored (but an error is logged to syslog(3))

--------------------
Bugs to Andrew <morgan@@parc.power.net> or the list <pam-list@@redhat.com>

########################################################################
# $Log: README,v $
# Revision 1.3  1997/01/04 20:42:43  morgan
# I want email on parc now
#
#@


1.1
log
@Initial revision
@
text
@@


1.1.1.1
log
@Initial import of virgin Linux-PAM 0.65, slightly stripped down.
@
text
@@


1.1.1.2
log
@Vendor import Linux PAM 0.75
@
text
@d1 1
a1 1
$Id: README,v 1.2 2000/12/04 19:02:35 baggins Exp $
d31 7
@

