04-01-2002
FreeBSD has a cool program to handle this called newsyslog. It's real easy to run it on other unix versions. You can get it via ftp from
here.
And don't let the name fool you, it's not just for syslog files.
10 More Discussions You Might Find Interesting
1. Programming
We have Sun OS 5.9 we are doing a backup process (ProC program) that uses the function...
fprintf(fp,"%s;%s;%s;%s;%s;%ld;%ld;%ld;%ld;%s;%s;%s;%d;%s;%s;%s;%ld;%s;%s;%s;%ld;%ld;%s;%ld;%s;%ld;%s;%s;%c%c",x_contrno, x_subno, x_b_subno,x_transdate,x_last_traffic_date,BillAmt_s, x_billamount_int,... (10 Replies)
Discussion started by: atiato
10 Replies
2. UNIX for Advanced & Expert Users
Does anyone know a way to determine the maximum filesize on a file system on Solaris, HP-UX, AIX, Linux, and OSF1 using the command line?
TIA (2 Replies)
Discussion started by: dknight
2 Replies
3. Solaris
I wants to ask that what is the max size of file that we can create in the unix file system. (2 Replies)
Discussion started by: sameerghogre
2 Replies
4. UNIX for Advanced & Expert Users
i want to know what is the maximum file size supported by linux with ext3 file system. (1 Reply)
Discussion started by: nagalenoj
1 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
We are running HP rp7400 box with hpux 11iv1.
Recently, we changed 3 kernel parameters
a) msgseg from 32560 to 32767
b) msgmnb from 65536 to 65535
c) msgssz from 128 to 256
Then we noticed that all application debug file size increase upto 2GB then it stops. So far we did not... (1 Reply)
Discussion started by: mhbd
1 Replies
6. SuSE
I'm trying to set the open files value to 4000 on a SLES 9 system.
Current values:ulimit -n
1024
I can set it using this:ulimit -n 4000
ulimit -n
4000
But this obviously sets it only for the shell session where I run the command to set it. I want to set this to 4000 for all time.
... (3 Replies)
Discussion started by: blowtorch
3 Replies
7. Solaris
There is a file in my Unix Server whose size will be constant.
But every day when the sheduled jobs run in the server, that file gets updated but the size does not change.
Upon doing file filename
It is dispalyed as a binary file.
Can anyone please explain how that file is created.
How is... (3 Replies)
Discussion started by: exterminator
3 Replies
8. UNIX for Dummies Questions & Answers
Hello All,
I am working on an issue, where I need to check the max file size of a file. If the file size exceeds 2 GB, then I need to generate an error message. Since the file system does not allow a file to be created larger than 2 GB, I am planning to use named pipes & AWK file to acheive my... (6 Replies)
Discussion started by: puru2121
6 Replies
9. AIX
I have a system with the following settings:
min:0.10
Assigned: 2.0
Max: 6.0
Partition is uncapped weight is 128.
I would like to know if even if this is uncapped, is the max it can use 6?
The actual pool has 16.
I remember reading about this somewhere but I don't remember can anyone... (3 Replies)
Discussion started by: techy1
3 Replies
10. Solaris
Hi,
I've compiled a 64-bit version of ClamAV 0.98.7 on my Solaris 10 SPARC server. I have a selection of files all containing the eicar signature but clamd is only picking up the signature in the files <2GB.
I have the following set in clamd.conf, to remove file size checking:
MaxScanSize 0... (4 Replies)
Discussion started by: Troutfest
4 Replies
LEARN ABOUT REDHAT
faillog
FAILLOG(8) System Manager's Manual FAILLOG(8)
NAME
faillog - examine faillog and set login failure limits
SYNOPSIS
faillog [-u login-name] [-a] [-t days]
[-m max] [-pr]
DESCRIPTION
faillog formats the contents of the failure log, /var/log/faillog, and maintains failure counts and limits. The order of the arguments to
faillog is significant. Each argument is processed immediately in the order given.
The -p flag causes failure entries to be printed in UID order. Entering -u login-name flag will cause the failure record for login-name
only to be printed. Entering -t days will cause only the failures more recent than days to be printed. The -t flag overrides the use of
-u. The -a flag causes all users to be selected. When used with the -p flag, this option selects all users who have ever had a login
failure. It is meaningless with the -r flag.
The -r flag is used to reset the count of login failures. Write access to /var/log/faillog is required for this option. Entering -u
login-name will cause only the failure count for login-name to be reset.
The -m flag is used to set the maximum number of login failures before the account is disabled. Write access to /var/log/faillog is
required for this option. Entering -m max will cause all accounts to be disabled after max failed logins occur. This may be modified with
-u login-name to limit this function to login-name only. Selecting a max value of 0 has the effect of not placing a limit on the number of
failed logins. The maximum failure count should always be 0 for root to prevent a denial of services attack against the system.
Options may be combined in virtually any fashion. Each -p, -r, and -m option will cause immediate execution using any -u or -t modifier.
CAVEATS
faillog only prints out users with no successful login since the last failure. To print out a user who has had a successful login since
their last failure, you must explicitly request the user with the -u flag, or print out all users with the -a flag.
Some systems may replace /var/log with /var/adm or /usr/adm.
FILES
/var/log/faillog - failure logging file
SEE ALSO
login(1), faillog(5)
AUTHOR
Julianne Frances Haugh (jockgrrl@ix.netcom.com)
FAILLOG(8)