01-23-2020
Also, I noticed (my guess) is that your application is related to predictive analytics and perhaps algorithmic trading.
In that case, these algorithms rely heavily on historical data and (often expensive) analytics.
I recommend you do not delete any of these "analytic files" unless you are sure you have backup copies.
May I ask why you are doing this (deleting analytical files which you believe to be unused)?
Are you having a disk space issue?
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have a directory which contains files.This Directory keeps getting in new files from time to time.I want to maintain only 15 files in that directory at any time and the old files should be deleted.
Eg:
Directory 'c' @'a/b/c contains:
1_a
2_a
3_a...
I want to delete all the old... (2 Replies)
Discussion started by: shiroh_1982
2 Replies
2. Programming
Hi All,
when I use the following analytic function in sql prompt, i am getting the result
count(emp_no) over (partition by emp_no )
/* select count(emp_no) over (partition by emp_no ) from temp */
but when i use the same analytic function in Pro*c i get the following error
Error... (2 Replies)
Discussion started by: quintet
2 Replies
3. Shell Programming and Scripting
So I have two files:
File1
pictures.txt 1.1 1.3
dance.txt 1.2 1.4
treehouse.txt 1.3 1.5
File2
pictures.txt 1.5 ref2313 1.4 ref2345 1.3 ref5432 1.2 ref4244
dance.txt 1.6 ref2342 1.5 ref2352 1.4 ref0695 1.3 ref5738 1.2 ref4948 1.1
treehouse.txt 1.6 ref8573 1.5 ref3284 1.4 ref5838... (24 Replies)
Discussion started by: linuxkid
24 Replies
4. Shell Programming and Scripting
Hi Friends,
I am new to this , I am working on AIX system and my scenario is to retrive the files from remote system and remove the files from the remote system after retreving files. I can able to retrieve the files but Can't remove files in remote system. Please check my code and help me out... (3 Replies)
Discussion started by: vinayparakala
3 Replies
5. Shell Programming and Scripting
Hi all, I have developed a shell script to copy the files from source to destination and simultaneously to delete the copied files in source. I can copy the files but the files cannot be deleted in source side. (3 Replies)
Discussion started by: Venkatesan
3 Replies
6. AIX
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies
7. AIX
Hi All,
I am trying to debug my core file using kdb.
When I try to get the stack trace I am facing this error.
core mapped from @ 700000000000000 to @ 70000000306fc04
Preserving 1680415 bytes of symbol table
Dump does not start with valid magic number
WARNING: Possibly truncated or... (2 Replies)
Discussion started by: Sachin1987
2 Replies
8. Shell Programming and Scripting
#!/bin/bash
#
name=$1
type=$2
number=1
for file in ./**
do
if
then
filenumber=00$number
elif
then
filenumber=0$number
fi
tempname="$name""$filenumber"."$type"
if (4 Replies)
Discussion started by: TheGreatGizmo
4 Replies
LEARN ABOUT DEBIAN
s3qllock
S3QLLOCK(1) S3QL S3QLLOCK(1)
NAME
s3qllock - Make trees on an S3QL file system immutable
SYNOPSIS
s3qllock [options] <directory>
DESCRIPTION
S3QL is a file system for online data storage. Before using S3QL, make sure to consult the full documentation (rather than just the man
pages which only briefly document the available userspace commands).
The s3qllock command makes a directory tree in an S3QL file system immutable. Immutable trees can no longer be changed in any way whatso-
ever. You can not add new files or directories and you can not change or delete existing files and directories. The only way to get rid of
an immutable tree is to use the s3qlrm command.
s3qllock can only be called by the user that mounted the file system and (if the file system was mounted with --allow-other or
--allow-root) the root user. This limitation might be removed in the future (see issue 155).
RATIONALE
Immutability is a feature designed for backups. Traditionally, backups have been made on external tape drives. Once a backup was made, the
tape drive was removed and locked somewhere in a shelf. This has the great advantage that the contents of the backup are now permanently
fixed. Nothing (short of physical destruction) can change or delete files in the backup.
In contrast, when backing up into an online storage system like S3QL, all backups are available every time the file system is mounted.
Nothing prevents a file in an old backup from being changed again later on. In the worst case, this may make your entire backup system
worthless. Imagine that your system gets infected by a nasty virus that simply deletes all files it can find -- if the virus is active
while the backup file system is mounted, the virus will destroy all your old backups as well!
Even if the possibility of a malicious virus or trojan horse is excluded, being able to change a backup after it has been made is generally
not a good idea. A common S3QL use case is to keep the file system mounted at all times and periodically create backups with rsync -a. This
allows every user to recover her files from a backup without having to call the system administrator. However, this also allows every user
to accidentally change or delete files in one of the old backups.
Making a backup immutable protects you against all these problems. Unless you happen to run into a virus that was specifically programmed
to attack S3QL file systems, backups can be neither deleted nor changed after they have been made immutable.
OPTIONS
The s3qllock command accepts the following options:
--debug
activate debugging output
--quiet
be really quiet
--version
just print program version and exit
EXIT STATUS
s3qllock returns exit code 0 if the operation succeeded and 1 if some error occurred.
SEE ALSO
The S3QL homepage is at http://code.google.com/p/s3ql/.
The full S3QL documentation should also be installed somewhere on your system, common locations are /usr/share/doc/s3ql or
/usr/local/doc/s3ql.
COPYRIGHT
2008-2011, Nikolaus Rath
1.11.1 August 27, 2014 S3QLLOCK(1)