Sponsored Content
Top Forums UNIX for Advanced & Expert Users Issue with IN_CLOSE_WRITE Event Of incrond Post 302886101 by Ariean on Wednesday 29th of January 2014 05:04:18 PM
Old 01-29-2014
Quote:
Originally Posted by Corona688
It is the uploader's job to move the file.

Only the uploader will know when it is complete.

If you cannot get the uploader to somehow signal completion, workarounds will be very ugly and potentially unreliable -- if you check timestamps, how can you tell the difference between a broken, stalled, or finished upload? You can't...
I just found that problem is with WINSCP client tool which user is using to drop the file and it creates a temporary file and renames it once it is done, incrontab thinks that it is temporary file open/close and sends that filename.part as input to the script. I came up with a script to strip and rename the file for further processing, thank you.
This User Gave Thanks to Ariean For This Post:
 
dat_evd_post_se(3DAT)				     Direct Access Transport Library Functions				     dat_evd_post_se(3DAT)

NAME
dat_evd_post_se - post Software event to the Event Dispatcher event queue SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_evd_post_se( IN DAT_EVD_HANDLE evd_handle, IN const DAT_EVENT *event ) PARAMETERS
evd_handle Handle for an instance of the Event Dispatcher event A pointer to a Consumer created Software Event. DESCRIPTION
The dat_evd_post_se() function posts Software events to the Event Dispatcher event queue. This is analogous to event arrival on the Event Dispatcher software Event Stream. The event that the Consumer provides adheres to the event format as defined in <dat.h>. The first element in the event provides the type of the event (DAT_EVENT_TYPE_SOFTWARE); the rest provide the event-type-specific parameters. These parame- ters are opaque to a Provider. Allocation and release of the memory referenced by the event pointer in a software event are the Consumer's responsibility. There is no ordering between events from different Event Streams. All the synchronization issues between multiple Consumer contexts trying to post events to an Event Dispatcher instance simultaneously are left to a Consumer. If the event queue is full, the operation is completed unsuccessfully and returns DAT_QUEUE_FULL. The event is not queued. The queue over- flow condition does takes place and, therefore, the asynchronous Event Dispatcher is not effected. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The evd_handle parameter is invalid. DAT_INVALID_PARAMETER The event parameter is invalid. DAT_QUEUE_FULL The Event Dispatcher queue is full. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.11 16 Jul 2004 dat_evd_post_se(3DAT)
All times are GMT -4. The time now is 11:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy