Jeffrey Butera wrote:
On Thursday 27 October 2005 05:55, John Jenkins wrote:
Alonzo
This is not really a database issue but an application usage iseue, and a
BASIC program or (on Unix) a check in the ,profile shell script is exactly
the way to do this.
We're on Unix and did this via the .profile route - works perfectly.
If your system supports pam (pluggable auth modules) you may want to
look at the limits.conf file. For example, on redhat its stored in
/etc/security/limits.conf
(there are other files there used to control other things via pam as well).
Here's a link that gives a few examples:
http://lists.debian.org/debian-user/2002/12/msg00210.html
Essentially, you can control a # of user-based resources, such as
maxlogins, and this can be on a user by user basis or applied to groups
# EXAMPLE /etc/security/limits.conf file:
# <domain> <type> <item> <value>
* - maxlogins 2
@faculty - maxlogins 4
% - maxlogins 30
%student - maxlogins 10
Explanation: every user can login 2 times, members of the faculty
group can login 4 times, there can be only 30 logins, only 10 from
students group.
Again, this works with stuff using pam only.
The .profile mechanism is one that works as well.
John
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
