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)
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)
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)
Hi, I am not root, but I need to limit the size of my directory, so that it cannot contain more than 200M of stuff inside. Is this possible?
Also, how can I see the total size of that directory? If I do ls -ltrd, it does not give me the size of all the files inside the directory. And if I do df... (6 Replies)
Hello
I want to limit the size of a directory;
so a user cant copy more staff inside it then 5 Giga for example..
eg. /nfs/temp/jhon size can not increase more that 5Gb
I havnt found anything on the net. Is there a way to do it? (2 Replies)
Hi
i configured log rotate for a specific file.
/var/log/sauer
i configured create a file in logrotate.d
# cat /etc/logrotate.d/sauer
#this is a logrotate configuration file for msu_ng logs
/var/log/sauer {
rotate 5
size=1M
daily
compress
... (5 Replies)
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)
I came across and unexpected behavior with redirections in tcsh. I know, csh is not best for redirections, but I'd like to understand what is happening here.
I have following script (called out_to_streams.csh):
#!/bin/tcsh -f
echo Redirected to STDOUT > /dev/stdout
echo Redirected to... (2 Replies)
Discussion started by: marcink
2 Replies
LEARN ABOUT SUSE
pdl::philosophy
PHILOSOPHY(1) User Contributed Perl Documentation PHILOSOPHY(1)NAME
PDL::Philosophy -- what's behind PDL?
DESCRIPTION
This is an attempt to summarize some of the common spirit between pdl developers in order to answer the question "Why PDL"? If you are a
PDL developer and I haven't caught your favorite ideas about PDL, please let me know!
An often-asked question is: Why not settle for some of the existing systems like Matlab or IDL or GnuPlot or whatever?
Major ideas
The first tenet of our philosophy is the "free software" idea: software being free has several advantages (less bugs because more people
see the code, you can have the source and port it to your own working environment with you, ... and of course, that you don't need to pay
anything).
The second idea is a pet peeve of many: many languages like matlab are pretty well suited for their specific tasks but for a different
application, you need to change to an entirely different tool and regear yourself mentally. Not to speak about doing an application that
does two things at once... Because we use Perl, we have the power and ease of perl syntax, regular expressions, hash tables etc at our
fingertips at all times. By extending an existing language, we start from a much healthier base than languages like matlab which have
grown into existence from a very small functionality at first and expanded little by little, making things look badly planned. We stand by
the Perl sayings: "simple things should be simple but complicated things should be possible" and "There is more than one way to do it"
(TIMTOWTDI).
The third idea is interoperability: we want to be able to use PDL to drive as many tools as possible, we can connect to OpenGL or Mesa for
graphics or whatever. There isn't anything out there that's really satisfactory as a tool and can do everything we want easily. And be
portable.
The fourth idea is related to PDL::PP and is Tuomas's personal favorite: code should only specify as little as possible redundant info. If
you find yourself writing very similar-looking code much of the time, all that code could probably be generated by a simple perl script.
The PDL C preprocessor takes this to an extreme.
Minor goals and purposes
We want speed. Optimally, it should ultimately (e.g. with the Perl compiler) be possible to compile PDL::PP subs to C and obtain the top
vectorized speeds on supercomputers. Also, we want to be able to calculate things at near top speed from inside perl, by using dataflow to
avoid memory allocation and deallocation (the overhead should ultimately be only a little over one indirect function call plus couple of
ifs per function in the pipe).
We want handy syntax. Want to do something and cannot do it easily? Tell us about it...
We want lots of goodies. A good mathematical library etc.
AUTHOR
Copyright(C) 1997 Tuomas J. Lukka (lukka@fas.harvard.edu). Redistribution in the same form is allowed but reprinting requires a permission
from the author.
perl v5.12.1 2009-10-17 PHILOSOPHY(1)