11-12-2007
no there's not. you need logrotate which is not a huge application (~40k). if you're so tight on space, you'll probably find that rewriting a bunch of commands in assembly language with only the functionality that you desire and linking to standard C calls will produce much much smaller binaries.
I've done this myself, and things like cat (which is about 10k) I rewrote in 42 bytes with basic error checking. rewrite a bunch of simple commands like that and you'll have room for logrotate (which you may not want to rewrite).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I limit size of a file to 1 MB or something like that under Linux? (4 Replies)
Discussion started by: _hp_
4 Replies
2. Solaris
I want to have a permanent file created - and limit the size that this file can grow.. I want a circular file..
ie max size of file is 10 mb.. and if any new data written to file the oldest data removed..
How can I do this?
I am on solaris 9 x86 (3 Replies)
Discussion started by: frustrated1
3 Replies
3. AIX
Can anybody help me?
How to increase file size limit in aix 5.2? I have already specified in /etc/security/limits file :
default:
fsize = -1
core = 2097151
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = 2000 (2 Replies)
Discussion started by: vjm
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
I have a problem writing or copying a file 2GB or larger to either the second or third disk on my C8000. I've searched this forum and found some good information on this but still nothing to solve the problem.
I'm running hpux 11i, JFS3.3 and disk version 4 (from fstyp) on all 3 disks.
... (2 Replies)
Discussion started by: HaidoodFaulkauf
2 Replies
5. UNIX for Advanced & Expert Users
I searched and could not find an answer to this, and am having difficulty, so I would appreciate any assistance that can be offered.
We're experiencing logs that are having all characters after the 850th one written being truncated. I am wondering if there is a default limit to the syslog... (1 Reply)
Discussion started by: Puck
1 Replies
6. UNIX for Dummies Questions & Answers
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (0 Replies)
Discussion started by: dewaraja
0 Replies
7. UNIX for Advanced & Expert Users
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (0 Replies)
Discussion started by: dewaraja
0 Replies
8. Shell Programming and Scripting
Everytime I try to start Discreet Flame on my Octane2 machine it keeps giving me an error message "initial log size exceeds limit--aborting"
Can anyone please help me how to fix this problem. Thanks.
Octane2
IRIX64 Release 6.5
Flame 2007 (6 Replies)
Discussion started by: dewaraja
6 Replies
9. Shell Programming and Scripting
Hi All,
I want to store 32KB of file in Oracle DB into CLOB field. I am not able to insert more than 32KB of file into CLOB. So i want to put a limit on the file size. I am using k shell.
My file size will dynamically increase its size, i want to check the file size if it is more than 32KB... (1 Reply)
Discussion started by: rajeshorpu
1 Replies
10. UNIX and Linux Applications
Just had a migration from Autosys 4.5 to R11.3.
After the migration to R11.3, Autosys jobs have been failing when the log file reaches a size of 800 MB.
This did not happen before the migration, when Autosys 4.5 was used.
Is there a way to configure the file size limit/cap in Autosys... (1 Reply)
Discussion started by: kimo222
1 Replies
LEARN ABOUT PLAN9
rewrite
REWRITE(6) Games Manual REWRITE(6)
NAME
rewrite - mail rewrite rules
SYNOPSIS
/mail/lib/rewrite
DESCRIPTION
Mail(1) uses rewrite rules to convert mail destinations into commands used to dispose of the mail. Each line of the file is a rule. Blank
lines and lines beginning with # are ignored.
Each rewriting rule consists of (up to) 4 strings:
pattern
A regular expression in the style of regexp(6). The pattern is applied to mail destination addresses. The pattern match is case-
insensitive and must match the entire address.
type The type of rule; see below.
arg1 An ed(1) style replacement string, with
standing for the text matched by the nth parenthesized subpattern.
arg2 Another ed(1) style replacement string.
In each of these fields the substring s is replaced by the login id of the sender and the substring l is replaced by the name of the
local machine.
When delivering a message, mail starts with the first rule and continues down the list until a pattern matches the destination address. It
then performs one of the following actions depending on the type of the rule:
>> Append the mail to the file indicated by expanding arg1, provided that file appears to be a valid mailbox.
| Pipe the mail through the command formed from concatenating the expanded arg1 and arg2.
alias Replace the address by the address(es) specified by expanding arg1 and recur.
translate
Replace the address by the address(es) output by the command formed by expanding arg1 and recur.
Mail expands the addresses recursively until each address has matched a >> or | rule or until the recursion depth indicates a rewriting
loop (currently 32).
If mail(1) is called with more than one address and several addresses match | rules and result in the same expanded arg1, the message is
delivered to all those addresses by a single command, composed by concatenating the common expanded arg1 and each expanded arg2. This mail
bundling is performed to reduce the number of times the same message is transmitted across a network. For example, with the following re-
write rule
([^!]*.att.com)!(.*) | "/mail/lib/qmail 's' 'net!1'" "'2'"
if user presotto runs the command
% mail research.att.com!ken research.att.com!rob
there will follow only one execution of the command
/mail/lib/qmail presotto net!research.att.com ken rob
Here /mail/lib/qmail is an rc(1) script used for locally queuing remote mail.
In the event of an error, the disposition of the mail depends on the name of the command executing the rewrite. If the command is called
mail and is run by $user, the command will print an error and deposit the message in /mail/box/$user/dead.letter. If the command is called
rmail, usually because it was invoked to deliver mail arriving over the network, the message will be returned to the sender. The returned
message will appear to have been sent by user postmaster.
SEE ALSO
mail(1)
REWRITE(6)