[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #DRV-310603]: -close switch

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #DRV-310603]: -close switch
  • Date: Thu, 03 Nov 2016 10:02:25 -0600
Erik,

> in the quote he writes 'The
> problem is that 'scour' is trying to remove files that are not closed'
> ..... should that be 'The
> problem is that 'scour' is trying to remove files that ARE closed'.
> 
> Meaning scour removes old files that are closed, but doesn't touch the open
> files, causing disk space to go missing?

Not quite. pqact(1) has the files open, but they're seen by scour(1) and deleted
from the file system. Unix allow this. pqact(1) continues to write the (still
open) files even though they're no longer visible.

> We might be better off using the close switch all the same.  In our
> pqact.conf file it seems most files are meant to be single one time
> transfers, because they include timestamps in the target file.  For example:
> 
> FILE -strip -overwrite WMO
> ^(WU)(US|AK|GM|CA|PU|HW|PA)(5.)(.)(K|P|T|N)(...)(.*)
> /u1/data/temp_vtec/\1\2\3\5\6.%H%M%S-%m%d%Y

A one-time file is good motivation for using the "-close" option.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: DRV-310603
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.