I tried your script and I didn't seem to have done anything. I copy and paste your script and run it as
and nothing happens.
I do need some help with re-generating/re-naming the files with however x.log.[n] file there is before I run the log rotation.
What am trying to do is kinda like checking a set of consecutive numbers and if there is a number sequence re-do the number sequence.
For example, if am suppose to have a series of number from 1 to 10 like 1.2.3.4.5.6.7.8.9.10 and suddenly I have it a number missing that it now becomes 1.2.5.7.9.10, then I need to re-generate the number to 1.2.3.4.5.6.
It's kinda like working on a set of array where some array numbers has been pop'ed hence you need to push up some of the members. Not sure if am explaining it correctly.
Hi
Can you suggest some perl script. My OS is HP-UX 11.11 I want to it into a cron job.
Every night it will backup the file with that day's date and open a dummy file.
Thanks
Ash (3 Replies)
Hello,
I only know the basic for shell programing. I need help for this, I thinks this is a basic for anyone who know a litle of shell scripting.
I need creat a script for a rotatate logs, when a filesystem is full. I have a filesystem.
The rotate consist in zip the current log (copy) and... (1 Reply)
I have a mac server. I have been having problems with my logs. My hard disk became full, when i researched into why it was full it was due to massive log files. There was barley any log rotation policies in place on the server. I tired to use logrotate. This doesn't work on my server. It is a MAC... (19 Replies)
I have a big log,separated by the character:,
one of the fields is the date in the format "day / month / year"
and I need to remove the lines prior to 30 days. Can help me? (7 Replies)
quick question:
I have a current script that will put the output on a log file. See snapshot of the code below. I wanted this to be rotated everyday based on date. So if anyone execute the script today there will be a filecreated such as sys.log.(datetoday), if tomorrow it would be... (1 Reply)
Hi,
Am trying to write my own version of a log rotate scripts 'coz I don't have the logrotate for other flavors of *nix servers. Probably should try and download the source and re-compile but our SA don't want to do so.
Anyway, just want to know if there is any way to improve on the code... (0 Replies)
Hi Experts,
I have script on crontab and give output quite large. I would like to know how to create rotate log when the size of log maximum 50MB
if the test.log is 50MB then create test.0
Thanks
Edy (2 Replies)
Hi,
I have below script in logrotate.d to rotate logs.
logs are not rotating after the file grow to 1k, do you have any idea? Is it because of it just only 1K?
Please let me know if the below syntax is in correct.
# more trotate
/sourcepath/*/servers/*/logs/*log... (2 Replies)
Discussion started by: lpprasad321
2 Replies
LEARN ABOUT OSF1
cdslinvchk
cdslinvchk(8) System Manager's Manual cdslinvchk(8)NAME
cdslinvchk - Checks the CDSL inventory of the base operating system and layered applications.
SYNOPSIS
/usr/sbin/cdslinvchk [log_file_path]
OPTIONS
The path name to a location for the log file. By default this will be /var/adm/cdsl_check_list.
DESCRIPTION
Use the cdslinvchk script to verify the current inventory of Context Dependent Symbolic Links (CDSLs) on a running system. CDSLs are spe-
cial symbolic links that enable a system to work in a cluster. If CDSLs are accidentally removed, your system will not function correctly
in a cluster. While this is not a problem for stand-alone systems, you may not be able to add the system as a member of a working cluster
at some future time. You can run this script at any time or configure it to run at system start-up, or as a cron task.
When you invoke the script, it checks the CDSLs on the running system against CDSLs of the installed inventory in /usr/.smdb and the addi-
tional entries in /var/adm/cdsl_admin.inv, and ensures that each target file exists on the system as a properly-constituted CDSL. If the
check is successful, the following message is displayed and the script terminates: Successful CDSL inventory check
If the script finds inconsistencies in the inventory, warning messages are displayed on your terminal and logged to the default log file at
/var/adm/cdsl_check_list. You can specify an alternate location for the log fill if required. The script locates any modified, missing,
or replaced CDSLs. Note that the previous copy of the log file is renamed and retained for reference and is renamed by appending to the
filename.
Refer to the System Administration guide for information on recreating any missing or broken CDSLs. Refer to the hier(5) reference page
for an inventory of CDSLs.
MESSAGES
One or more of the following messages may be displayed and logged to the log file: Unable to create <pathname> report file -- the script
was not able to create a log file. Check the target directory and security. Expected CDSL: <cdsl_pathname> -> <pathname> CDSL Target has
been modified to: <pathname> CDSL has been replaced with <pathname> CDSL is missing Failed CDSL inventory check. See details in <log file>
FILES
Additional inventory file entries. This file will not exist on all systems. The current and previous log files for inventory errors and
messages
SEE ALSO
Commands: cron(8)
Others: hier(5)
See also the System Administration guide for details of CDSLs
cdslinvchk(8)