How control time on/login freq?

How control time on/login freq?

Post by Jamie Sike » Tue, 31 Mar 1998 04:00:00

> I am running a internet server using Linux redhat 3.0.3.  There is one dial
> in line from outside.  Actual login validation is done using passwd/group.
> Dial in Users are using PPP.  Are there scripts available to control how
> frequent and how long a user can use the dial in line?

Use one of the software searchers to hunt up "autolog" and/or "idled".
I've read they will log off unused terminals, but they might have
other features or be found with other software that does what you want.

1. PCI bus freq with CPU freq at (X * 40)Mhz?

: Sorry for ignorance, but what will be the frequency on a PC's PCI bus
: when the CPU runs at main frequency of 40MHz (DX2/80, DX4/120 i.e.)?

: I always thought that PCI will than run at 40MHz too.
: But was told today that it will be only 20MHz?!  Oh God.
: How can I check this for sure, without running hated benchmarks,
: but only by exploration of MB jumpers?

PCI is specified to run at up to 33MHz.  To accomodate faster CPU
clocks motherboards can provide the facility for PCI to run at
some fraction of the CPU.  My motherboard (GA-486AMS) allows a
CPU:PCI ratio of 1:1 or 2:1, configured in the BIOS setup.  In
principle other ratios could be used (e.g. 4:3), but I'm not aware
of any motherboards which support this.

Having said that, I have run PCI at 40MHz with a DX4-120, and it
worked (with AHA-2940 and S3-968).  This made little or no difference
to kernel build times compared to 20MHz, although this is a crude
benchmark.  Doing this could reduce the life expectancy of PCI

(A recent version of the PCI spec (2.1?) allows for faster clocks,
but I don't think there are many compliant cards available).

: I was also told that having 40MHz will probably cause
: an addition of extra wait states for cache and RAM access,
: thus making a box considerably _slower_ for real work
: than with 33MHz CPU main frequency, especially for UNIX-like OS
: (FreeBSD in my case, but who cares).  Any comments on this one?

With 15ns cache and 70ns SIMMs I was able to run a DX4-120 with
0WS and 2-1-1-1 cache burst read, the fastest settings supported.
This is probably motherboard dependent.

: And, in case both statements are true, why bother looking
: at (X * 40)MHz 486 CPUs at all?

They are more of a win with VLB motherboards.

: P.S. I don't own a PCI box, but just planning to buy one, choosing
:      the best bang-per-buck configuration now.
:      Was considering AMD 160MHz (glorified 486, called 5x86, he-he :)
:      chip, which has 40MHz main freq and 4x multiplier.

This is the 5x86-133, it's only 160MHz if you overclock it, and then you're
back where you started...

:      Now I'm seriously considering AMD 133 part (this one is 33MHz, 4x).
:      Guys have a very nice opinions on it.

For PCI, the AMD 5x86-133 makes more sense.  I'm running one now,
and very happy with it.


2. Security issue ? Env Var set from CGI C program caused a program failure

3. Login/time control

4. X Protocol Compressor - dxpc - improved version 0.4 available

5. controlling number of times getty or login asks for userid/password

6. Freeing Ports

7. controlling login time on Linux

8. Linux on an extended partition

9. Monitor Timing for IBM 5081 Fixed Freq. Monitor.

10. arch/alpha/kernel/time.c - override bogus clock freq gues ses

11. Restricting dialup user logins / login times?

12. How to last login date for a user at login time??

13. Finding user login time and logout time with terminal details