Sponsored Content
Top Forums UNIX for Advanced & Expert Users Issue with IN_CLOSE_WRITE Event Of incrond Post 302886048 by Ariean on Wednesday 29th of January 2014 12:49:56 PM
Old 01-29-2014
Quote:
Originally Posted by Corona688
Have the uploader move the file to its final location when its done uploading. Make the two folders on the same partition. That way, complete files will appear in the folder with no intermediate state.
Uploader/Client can put a file in one location, i have to come up with the script to move the file to a different directory. But since the file system event is triggered/ing even before the file has been completely transfered, i can't move the file as it will move only partial file? isn't it. please correct me if i am wrong.

For Example:
In the below script move_to_directory if i put a line to move the file, it will move only partial file

Code:
/var/sftp/home/aac IN_CLOSE_WRITE move_to_directory

mv folder1/file1 folder2/file1
 
event_class(5)															    event_class(5)

NAME
event class file - The file that contains the declaration of an event class. DESCRIPTION
Audit events can be logically grouped into event classes. Event classes are defined in event class files. An event class file contains an event class number and a list of event numbers corresponding to audit events. All event class files must be created in the dcelocal/etc/audit/ec directory. The name of the event class file becomes the name of the event class. The recommended naming convention for event class files is: dce_server-name_class where class is a descriptive text that characterizes the event class. Event class files must be write-protected by the local operating system (that is, only administrators should have write access to these files). Audit clients read these files to maintain an event table in their address space. Optionally, an event class file can contain a SEP line. This line contains a list of prefixes of the event numbers in the file. The SEP line speeds up the scanning performed by the Audit clients. Audit clients which do not have events with one of the prefixes listed will not scan the event list. If the SEP line is not provided in the file, Audit clients will have to read the entire file to find out if the event class file contains any of their events. Empty lines are ignored in the event class file. Comments are designated by the number sign (#) placed before the comment text. The Event Class File Format The format of an event class file is: ECN=event_class_number SEP=prefix_1 prefix_2 ... # comments start with the number sign event_num- ber_1 event_number_2 EXAMPLES
Following is an example of an event class file for the event class ec_local_authentication: ECN = 0x00000001 SEP = 0x100 # AS_Request 0x00000100 # TGS_TicketReq 0x00000101 # TGS_RenewReq 0x00000102 # TGS_ValidateReq 0x00000103 event_class(5)
All times are GMT -4. The time now is 06:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy