Sponsored Content
Top Forums Shell Programming and Scripting Building a better mouse trap, or How many lines of code does it take to trap a mouse? Post 302070681 by mph on Thursday 6th of April 2006 03:04:40 PM
Old 04-06-2006
Perderabo,

Quote:
Not sure that I understand. Is this one directory or a directory tree? How the the files get removed? Anyway...
This is a directory tree /ftp. Under this there are the users and their incoming and outgoing directories. Each user has their own directory for security reasons. Our customers don't want their data availible to the wrong vendors.
Files get removed by another daily cron job that finds files older than 10 days. The date can't be trusted as far as how many minutes old they are. So, find works fine for removing old the files. If they're transferred via CIFS it holds the creation date previous to the transfer. That's why I use the -cmin. It seems to work well and uses the access time of the transfer. But I think that's where some files fall through. I had to setup ntp on the server due to clock variations between the server and the clients causing problems with file times. Another reason to use the "find all files and diff them" logic.
Quote:
I would loop through all the files getting name and size (if date cannot be trusted, ignore it). Add name and size to a little database somewhere, timestamping this addition. Or if the entry is present, update size and timestamp. Then loop through database and find entries with old timestamps; process these; remove from database and directory (removal not possible? --- mark as processed in the database.)
This is simular to what (I guess) I was trying to say with the idea I was looking into. That is to say, find all the files under /ftp/*/outgoing and diff them for additions against the file list built 5 minutes ago. Using the diffed file names, the "database" would simply be a temp file containing the name and size. Grep for the file, awk the $NF for the size and compair till they're the same, sleeping for bit between checks to avoid frantic looping. When the run is finished delete the temp database. Removed files won't be an issue, since I'm only looking for added files between runs. If the file reapears, there's usually a good reason for it (corrupted IGES files, etc...) and the vendor should be re-notified.

I hope this makes sense. My fingers are too well connected to my brain.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Mouse wheel...

Hello. I've got round to installing RedHat 7.1, and i have this slight problem. I'm not able to use my mouse wheel. Is this just not possible in RedHat or is there a way to configure my mouse so i can use my mouse wheel. Thank you. (1 Reply)
Discussion started by: Mr-Pixie
1 Replies

2. Linux

Mouse Problems

I just got the other computer working again and i put Fedora Core 2 on it but theres a problem. It wont recongnize my mouse at all. Not in installation or in the actual desktop... it doesnt even know its there. It says No - Mouse.... does anyone know how i can fix this? (4 Replies)
Discussion started by: FordGuy
4 Replies

3. UNIX for Advanced & Expert Users

Indigo mouse

A few years ago i found i the Net a "homework" about how to convert ps2 mouse to Indigo mouse. But i do not save it. Anybody helps me? There are about 10 Indigo mice in all of my country. Thanks in advance (2 Replies)
Discussion started by: mikidimov
2 Replies

4. HP-UX

reset mouse

I have a Belkin KVM switcher, but when I switch from Unix to Windows, then back to Unix, the mouse stops working is there any way to reset the mouse without restarting the workstation? thanks! (0 Replies)
Discussion started by: xRonin
0 Replies

5. UNIX for Dummies Questions & Answers

Changing middle mouse button for pasting to right mouse button in cygwin rxvt

Hi, I'm using rxvt in Cygwin and I'm wondering how to change my mouse bindings from the middle button for pasting to the right button. The main reason why I want to do this is because my laptop doesn't have a middle mouse button. Thanks for any help! (2 Replies)
Discussion started by: sayeo
2 Replies

6. Shell Programming and Scripting

Cntl+z Trap is not detecting ??? Help required to add a trap detection ???

Hi folks, I have tried to add some trap detection in the below script....this script is used to monitor database activities...in a rather awkward way :rolleyes:.... The idea behind adding trap is that....this script creates lots of temporary files in the running folder to store the count... (1 Reply)
Discussion started by: frozensmilz
1 Replies

7. What is on Your Mind?

Keyboard vs mouse

Which Input device do you use the most ? for me... keyboard ofcourse !! (56 Replies)
Discussion started by: vpraveen84
56 Replies

8. Homework & Coursework Questions

VM trap may work differently than a pure install trap.

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: That is the last reply I received from my instructor, and I'm looking for some alternatives. When using... (2 Replies)
Discussion started by: newuser45
2 Replies
ASLMANAGER(8)						    BSD System Manager's Manual 					     ASLMANAGER(8)

NAME
aslmanager -- Apple System Log data life-cycle manager SYNOPSIS
aslmanager [-s store_dir] [-a [archive_dir]] [-ttl days] [-store_ttl days] [-module_ttl days] [-size max_size] [-asldb] [-module [name]] [-checkpoint] [-d [level]] [-dd [level]] DESCRIPTION
aslmanager manages rotated files and ASL data written by the syslogd server. It is started automatically at various times by syslogd. It may also be invoked from the command line by the superuser (root). It manages the life-cycle of data in the ASL database, rotated log files, and ASL directory data stores. Configuration information for aslmanager comes from the /etc/asl.conf configuration file, any ASL output mod- ule configuration files in the /etc/asl directory, and from command-line options that may be specified to override some settings found in the configuration files. In normal operation, it first checks the ASL database in /var/log/asl, then it checks the files and directories speci- fied by /etc/asl.conf and each ASL output module. If the -asldb flag is specified, then only the ASL database will be processed. If the -module flag is specified, then the ASL database will not be processed. All ASL output modules, or a single module if name is speci- fied, will be processed. If -checkpoint is specified, then aslmanager will signal syslogd to checkpoint files for all modules, or for a single named module, before processing. The -d flag causes aslmanager to print debug messages tracing it's actions as they are performed. An integer value (1, 2, or 3) may follow the -d flag. Higher values cause more fine-grained messages to be printed. The default value is 1. The -dd flag directs aslmanager to do a ``dry run''. Debug messages are printed as with -d, but no actions are actually performed. An optional debug level may follow the -dd flag. ASL DATABASE MANAGEMENT aslmanager scans the ASL database in /var/log/asl, or some other path specified by the setting of the ``store_path'' parameter in asl.conf, or by the path supplied following the -s flag. Data files that are older than the time-to-live for the database are either archived or removed. Files that contain messages with explicit expire times are removed or archived monthly after all their contents expire. The default 7 day time-to-live value may be overridden by the setting of the ``store_ttl'' parameter in asl.conf or by supplying a value follow- ing the -store_ttl flag or the -ttl flag (which overrides the time-to-live for both the ASL database and for all ASL modules). A time-to- live value of zero allows files to remain in the store with no time limit. A maximum size for the entire database is provided by the setting of the ``max_store_size'' parameter in asl.conf, or as a value following the -size flag. This will cause aslmanager to archive (if enabled) and remove files to keep the database size below the specified limit. The default value is 150000000 bytes. A value of zero means the size is unlimited. An unlimited size specification should be used with great caution, since a runaway process could quickly fill all available disk space. Files are removed in order starting from oldest to new- est. Files with the same date are removed in standard lexicographic sort order by file name. Files are either removed entirely or copied to an archive directory. If the -a flag is specified with no argument, files are copied to the /var/log/asl.archive directory. An alternate directory path may be specified following the -a flag. The archive parameter setting in asl.conf enables or disables archiving. The archive parameter requires a value of "1" to enable archiving, or a value of "0" to disable it. An option archive directory path may follow the "0" or "1". ASL OUTPUT MODULE MANAGEMENT For each ASL output module, or a single module specified as an argument following -module, aslmanager first locates all checkpoint files pro- duced by syslogd for that module. aslmanager checks all ASL directory data stores and all rotated log files - those with a ``rotate'' option in the module's configuration rules. Checkpoint files are renamed if necessary to conform to the naming style specified for the file by a ``style'' option in the module's configuration file. aslmanager will compress the file if directed by a ``compress'' option, and it will move the file to a destination directory if a ``dest'' option is specified for the file. Following this, aslmanager will delete expired files. The time-to-live for files is 7 days by default, but may be specified using the ``ttl'' option for the file in the module's configu- ration rules. If -module_ttl or -ttl are specified command line, then value specified as an argument is used as a time-to-live instead. -module_ttl specifies time-to-live for module processing. -ttl specifies time-to-live for both the ASL database and for modules. Finally, if the ``all_max'' option is specified for the output file, aslmanager checks the total size of all the rotated versions, and will delete them, (oldest first) to limit the total size as specified by ``all_max''. When processing ASL directory data stores, aslmanager will similarly delete data files after the expiry of their time-to-live, and will delete data files (oldest first) to limit the total size as specified by ``all_max''. SEE ALSO
syslogd(8), syslog(1), asl(3), asl.conf(5), syslog(3). HISTORY
The aslmanager utility appeared in Mac OS X 10.6. Support for log file and ASL directory life-cycle management was added in OS X 10.9. Mac OS X December 7, 2007 Mac OS X
All times are GMT -4. The time now is 09:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy