toggle quoted messageShow quoted text
As far as I can see from your recv.ini and recv-channels.ini, you have got the correct tmp folders in recv-channels.ini and the entry under parameters in recv.ini is not necessary.
Best regards - Alan S
On 06/03/2011 3:16 PM, Ulrich G. Kliegis wrote:
I love this physicist's approach, do we see what we think to see? Oh well.
> Just to check, you /do/ have a tmp_directory entry in your recv.ini:
> pointing to the same partition as all the other receive directories?
How could this box run for years without the tmp definition in the
section - don't ask me why, when, how, this recv.ini file was ported from
installation to installation... At least, there was no tmp_directory entry.
Now, as in my special (really that special?) setup where I want metop and
MSG data to be on different disks (having the least possible data
movements and maximized storage space in mind), how do I achieve that? I
have two target partitions, but the tmp obviously has to be on only one of
them. If that is the case, then the final files will be composed on only
partition but will be shifted to the other later on.
Alternatively, I could bring both together now on a single terabyte or
disk. What has more advantages?
This is the content of the present recv.ini file, and note that I added
pointer only minutes ago, being aware that it is only 21, half the
reflected in the missed packets rate.
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver
# additional files: see license.ini, recv-channels.ini (optional)
# for more information on file format use help menu in Tellicast shell
# 2-4-3 10-10-2005
name=TSL Announcement Channel
# the previous line added 2011-03-06 - or should this point to R: too?
# recv-channels.ini - TelliCast+TelliVision Client channel configuration
# 2-4-3 10-10-2005
[EUMETSAT Data Channel 1]
# Section per channel or channel group identified by
# channel name (wildcard "*" allowed at end of name)
# priority: priority of this channel/channel group reception
# in case reception would case reception bandwidth sum
# to exceed "recv.ini [parameters] total_bandwidth"
# 0=highest; 1000=lowest
# (default: 500=medium priority)
# target_directory: directory for received files.
# The target_directory name is relative to the current
# (default: ./received)
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)
# temp_directory: If this parameter is given tqrecv will internally
# store/compose all received files within the given
# directory and later move them to the target directory.
# While this option requires an additional move
# operation it guarantees that all files appearing in
# the target directory are fully written to the file
# (default: undefined=off
# but default value may be redefined in recv.ini)
[EUMETSAT Data Channel 2]
[EUMETSAT Data Channel 3]
[EUMETSAT Data Channel 4]
target_directory=F:\received\Data Channel 4
[EUMETSAT Data Channel 5]
[EUMETSAT Data Channel 6]
What I thought about more than once is to draft a graphical description of
the data path - describing the various instances where the data pass
through and what happens where... Kind of a workflow map.
Again and again, I am desoriented by the various receiving directories...
Cheers, and thanks in advance for a new re-railing...