03-10-2005
prevent file size is too large
We have EDP members will do some testing job in my system , but sometimes these process will generate some error to the system log or any file ( usually the members don't know the log is reached to this level ) , then make the system crashed , could suggest the way how can to prevent this problem ? eg. restrict the file size . thx
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi, Im trying to take a database backup. one of the files is 26 GB. I am using cp -pr to create a backup copy of the database. after the copying is complete, if i do du -hrs on the folders i saw a difference of 2GB.
The weird fact is that the BACKUP folder was 2 GB more than the original one!
... (1 Reply)
Discussion started by: 0ktalmagik
1 Replies
2. UNIX for Dummies Questions & Answers
I would like to edit a doc which is large file size. I can't use "vi" command due to out of memory.
$ vi large.dat
ex: 0602-101 Out of memory saving lines for undo.
Please help. Thanks. (2 Replies)
Discussion started by: Rock
2 Replies
3. Shell Programming and Scripting
Hi,
I have a large file with a repeating pattern in it. Now i want the file split into the block of patterns with a specified no. of lines in each file.
i.e. The file is like
1...
2...
2...
3...
1...
2...
3...
1...
2...
2...
2...
2...
2...
3...
where 1 is the start of the block... (5 Replies)
Discussion started by: sudhamacs
5 Replies
4. Shell Programming and Scripting
Hi
I am new to shell scripting.I want to create a batch file which creates a desired number of files with a specific size say 1MB each to consume space.How can i go about it using for loop /any other loop condition using shell script?
Thanks (3 Replies)
Discussion started by: swatideswal
3 Replies
5. Shell Programming and Scripting
Hi Experts,
My requirement is to compare the second field/column in two files, if the second column is same in both the files then compare the first field. If the first is not matching then print the first and second fields of both the files.
first file (a .txt)
< 1210018971FF0000,... (6 Replies)
Discussion started by: krao
6 Replies
6. UNIX for Advanced & Expert Users
We're running Solaris 7 on FDDI n/w on an E6500 host and wish to use MTU (packet size) > 1500, more like 3072 bytes to begin with and possibly up to 4096 bytes.
Linux has /etc/network/interfaces. Does ANYONE remember the equivalent in Unix? When I do ifconfig eth0 mtu 4000, I get the error... (0 Replies)
Discussion started by: sharique
0 Replies
7. Solaris
Greetings, I'm stuck in a time warp using ancient machines from the prehistoric era that should be rightfully displayed in the Smithsonian.
We're running Solaris 7 on FDDI n/w on an E6500 host and wish to use MTU (packet size) > 1500, more like 3072 bytes to begin with and possibly up to 4096... (9 Replies)
Discussion started by: sharique
9 Replies
8. Red Hat
Hi,
I've some directory that I used as working directory for a program. At the end of the procedure, the content is deleted. This directory, when I do a ls -l, appears to still take up some space. After a little research, I've seen on a another board of this forum that it's not really taking... (5 Replies)
Discussion started by: bdx
5 Replies
9. Shell Programming and Scripting
Hi All,
This is my first post here. Hoping to share and gain knowledge from this great forum !!!!
I've scanned this forum before posting my problem here, but I'm afraid I couldn't find any thread that addresses this exact problem.
I'm trying to split a large XML file (with multiple tag... (7 Replies)
Discussion started by: Aviktheory11
7 Replies
10. Shell Programming and Scripting
Hi,
I wrote a shell script, which let me manage dns records through an api.
The raw core-command looks like about this:
output="$(curl -X GET https://mgt.myserver.de:8081/api/v1/servers/localhost/zones)"The output contains a list of all zones with all records and is about 800 Kilobytes... (9 Replies)
Discussion started by: stomp
9 Replies
LEARN ABOUT HPUX
vxcmdlog
vxcmdlog(1M) vxcmdlog(1M)
NAME
vxcmdlog - administer command logging
SYNOPSIS
vxcmdlog [-H] [-l] [-m {on|off}] [-n number] [-s size]
DESCRIPTION
The vxcmdlog command is used to administer command logging in Veritas Volume Manager (VxVM). This feature can be used to record all VxVM
commands that are issued, and can be used in conjunction with the transaction logging feature (see vxtranslog(1M)).
When the current log file reaches a maximum size, it is renamed as a historic log file, and a new current log file is created. A limited
number of historic log files is preserved to avoid filling up the file system.
Each log file contains a header that records the host name, host ID, and the date and time that the log was created. See the EXAMPLES sec-
tion below for a description of the entries that are recorded in a log file.
OPTIONS
-H Displays detailed help about the usage of the command.
-l Lists current settings for command logging. This shows whether command logging is enabled, the maximum number of historic log
files, and the maximum log file size.
-m {on|off}
Turns command logging on or off. By default, command logging is turned on.
-n number Sets the maximum number of historic log files to maintain. The default number is 5. If number is set to no_limit, there is no
limit on the number of historic log files that are created.
-s size Sets the maximum size to which a command log can grow. (Note that this setting has no effect on existing historic log files.)
The suffix modifiers k, m, and g may be used express sizes in kilobytes, megabytes and gigabytes respectively. If no suffix is
specified, the default units are kilobytes.
If size is set to no_limit, there is no limit on the size of the log file.
The size of the command log is checked after an entry has been written so the actual size may be slightly larger than that speci-
fied. When the log reaches the specified size, the current command log file, cmdlog, is renamed as the next available historic
log file, cmdlog.number, where number is an integer from 1 up to the maximum number of historic log files that is currently
defined.
If the maximum number of historic log files has been reached, the oldest historic log file is removed, and the current log file
is renamed as that file.
The default maximum size of the command log file is 1m(1MB).
EXAMPLES
Turn on command logging:
vxcmdlog -m on
Set the maximum command log file size to 512KB:
vxcmdlog -s 512k
Set the maximum number of historic command log files to 10:
vxcmdlog -n 10
The following are sample entries from a command log file:
/usr/sbin/vxdctl mode
/usr/sbin/vxdisk -q -o alldgs list
/etc/vx/diag.d/vxprivutil dumpconfig /dev/vx/rdmp/Disk_4s2
/usr/sbin/vxdisk list SENA0_1
Each entry usually contains a client ID that identifies the command connection to the vxconfigd daemon, the process ID of the command, a
time stamp, and the command that was used together with its arguments. If the client ID is 0, as in the third entry shown here, this means
that the command did not open a connection to vxconfigd.
Note: The client ID is the same as that recorded for the corresponding transactions in the transactions log.
FILES
/etc/vx/log Symbolic link to the log directory. This can be redefined if necessary.
/etc/vx/log/cmdlog Current command log.
/etc/vx/log/cmdlog.number
Historic command logs.
NOTES
If vxcmdlog records the invocation of a vxmake command that reads object definitions from a description file, vxcmdlog additionally records
the contents of the description file.
Most command scripts are not logged, but the command binaries that they call are logged. Exceptions are the vxdisksetup, vxinstall, and
vxdiskunsetup scripts, which are logged.
SEE ALSO
vxtranslog(1M)
Veritas Volume Manager Troubleshooting Guide
VxVM 5.0.31.1 24 Mar 2008 vxcmdlog(1M)