Date   
Re: not yet perfect, but...

David J Taylor
 

David,
Thank you for the info on the Tellicast versions. I have checked and am
running 2.4.4a, which gives me no trouble and as it ain't broke, I'm not
going to fix it. When the new release is finally made with all the
improvements, I will probably upgrade.

Best regards - Alan S
2.4.4a is the latest released version, Alan, so there's no suggestion that you should upgrade. I did not mean to give that impression. There /will/ be a new version at some point in the future, and it's possible that it will eventually become a mandatory update some time after its release.

2.4.4a works a little better than the 2.5.17 version, in fact!

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

David J Taylor
 

What could have happened when the T-Systems-software didn't find it's
t(e)mp folders? It works with tmp... now, but also worked with temp - and
since I upgraded to the Big Toro dish, I had no missing frames any more
(had them with the old Thomson dish).

But this doesn't cure my (diagnosis-induced) symptoms yet...
Sorry, can't deny my background... ;/

Cheers,

U.
Ulrich, without the tmp_directory, TelliCast will build up the final files in situ, so that there is a danger that programs will try and use the data before it is complete. My own software tries to guard against this, of course, but having the tmp_directory helps ensure file integrity.

On one underpowered PC I have put the tmp_directory on RAMdisk to reduce losses, but that was a single-core PC receiving all the data, including a full Metop stream. (This with the newer 2.5.17 client which does not use FSY files).

Your losses seem to be strongly correlated with data throughput. I do notice that your throughput seems a lot higher than I would expect for a SkyStar card. My main PC, which takes Meteosat-9 full scan, EARS AVHRR, Metop AVHRR, and MODIS-L1 data, has a daily throughput of 400kB/s, whereas yours seems to be in excess of 800kB/s.

http://www.satsignal.eu/mrtg/feenix_dvb.html
http://eumetmon.rummelecke.de/windbuedel_dvb.html

No chance you've left the "*" entry somewhere in recv-channels.ini? It seems unlikely, as you would rapidly run out of disk space! But why is your throughput twice mine? If you aren't using IASI or GOME data, I would suggest commenting out the entries in recv-channels.ini for the moment.

What version of the SkyStar and TelliCast software do you have?

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Alan Sewards
 

David,
Thank you for the info on the Tellicast versions. I have checked and am running 2.4.4a, which gives me no trouble and as it ain't broke, I'm not going to fix it. When the new release is finally made with all the improvements, I will probably upgrade.

Best regards - Alan S

On 07/03/2011 8:13 AM, David J Taylor wrote:
Hi folks,
I'd just like to note that in the early T-Systems software the syntax
for the temp_directory was temp_directory= in the recv.ini and
recv_channels.ini file comments. A few years ago, during one of the
updates of the software, this got re-spelled as tmp_Directory= . My
recv_channels.ini still has the temp spelling but I may well still be
running the older software, that computer has been running for three
years now.

I think with most OS, a move is easier than a copy.

Best regards - Alan S
Alan,

Thanks for the note on the syntax on earlier versions.

If you are not running either version 2.4.4 B or version 2.4.4a of the
TelliCast client I would suggest that you update. Either of those two
versions is OK, but older versions may have problems with some of today's
data. 2.4.4a appears to date back to October 2006.

Cheers,
David
--
Alan Sewards
email: alan@...
web site: http://asewards.free.fr

Re: not yet perfect, but...

David J Taylor
 

Hi folks,
I'd just like to note that in the early T-Systems software the syntax
for the temp_directory was temp_directory= in the recv.ini and
recv_channels.ini file comments. A few years ago, during one of the
updates of the software, this got re-spelled as tmp_Directory= . My
recv_channels.ini still has the temp spelling but I may well still be
running the older software, that computer has been running for three
years now.

I think with most OS, a move is easier than a copy.

Best regards - Alan S
Alan,

Thanks for the note on the syntax on earlier versions.

If you are not running either version 2.4.4 B or version 2.4.4a of the TelliCast client I would suggest that you update. Either of those two versions is OK, but older versions may have problems with some of today's data. 2.4.4a appears to date back to October 2006.

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

I'd just like to note that in the early T-Systems software the syntax
for
the temp_directory was temp_directory= in the recv.ini and
recv_channels.ini file comments.
Alan,
that's what my memory also told me. I kept the ini-files through the version
change, if I remember correctly.

What could have happened when the T-Systems-software didn't find it's
t(e)mp folders? It works with tmp... now, but also worked with temp - and
since I upgraded to the Big Toro dish, I had no missing frames any more
(had them with the old Thomson dish).

But this doesn't cure my (diagnosis-induced) symptoms yet...
Sorry, can't deny my background... ;/

Cheers,

U.

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: MSG-1@...
Von: "ernstlobsiger" <ernst.lobsiger@...>
Datum: Sun, 06 Mar 2011 19:15:23 -0000
Betreff: [MSG-1] Re: not yet perfect, but...
Antwort an: MSG-1@...

What I recommend is to # comment out the "tmp_directory" entry in
recv.ini and use "tmp_directory" entries in recv-channels.ini only.
Done already hours ago... :) Even more: I deleted the line!

When I had changed all temp...-entries to tmp* in recv-channels.ini, I first
thought, bingo!, that was it! several minutes no missed packet appearing in
the tellicasts statistics.

Then, all of a sudden, "hell broke lose" again - and I saw that that was the
same time that the life AVHRR data from NOAA came in. At least a coarse
coincidence. Then a non-maskable interrupt happened: My wife called me
for dinner. So, I couldn't pursue it any further at that time...

Cheers,
U.

Re: not yet perfect, but...

Alan Sewards
 

Hi folks,
I'd just like to note that in the early T-Systems software the syntax for the temp_directory was temp_directory= in the recv.ini and recv_channels.ini file comments. A few years ago, during one of the updates of the software, this got re-spelled as tmp_Directory= . My recv_channels.ini still has the temp spelling but I may well still be running the older software, that computer has been running for three years now.

I think with most OS, a move is easier than a copy.

Best regards - Alan S

On 06/03/2011 8:21 PM, David J Taylor wrote:
> Hmm, Alan Sewards says it is not necessary since the pointers are in the
> recv-channels.ini file.
>
> I don't dare to ask, who's right, but rather, what is recommended?

Both are correct.

- If you have a single &#92;received&#92; directory tree, then only the recv.ini
entry is required, but it is not provided by default.

- With separate disks for certain &#92;received&#92; directories, then a
per-channel tmp_directory entry is required, pointing to the same
partition as the &#92;received&#92; directory.

- Having two partitions on the same hard disk, for separate &#92;received&#92;
directories is not recommended.

Nothing new in the above, but perhaps clarifying what I said before. Yes,
it's still true even with NTFS that a rename (on the same partition) is a
much cheaper operation than a disk-to-disk copy.

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...
<mailto:david-taylor%40blueyonder.co.uk>

--
Alan Sewards
email: alan@...
web site: http://asewards.free.fr

Re: not yet perfect, but...

David J Taylor
 

Hmm, Alan Sewards says it is not necessary since the pointers are in the
recv-channels.ini file.

I don't dare to ask, who's right, but rather, what is recommended?
Both are correct.

- If you have a single &#92;received&#92; directory tree, then only the recv.ini entry is required, but it is not provided by default.

- With separate disks for certain &#92;received&#92; directories, then a per-channel tmp_directory entry is required, pointing to the same partition as the &#92;received&#92; directory.

- Having two partitions on the same hard disk, for separate &#92;received&#92; directories is not recommended.

Nothing new in the above, but perhaps clarifying what I said before. Yes, it's still true even with NTFS that a rename (on the same partition) is a much cheaper operation than a disk-to-disk copy.

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

ernstlobsiger
 

--- In MSG-1@..., "Ulrich G. Kliegis" <Ulrich.Kliegis@...> wrote:



An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Sun, 6 Mar 2011 17:29:20 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

Just to check, you /do/ have a tmp_directory entry in your
recv.ini:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive
directories?
How could this box run for years without the tmp definition in the
parameters 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.
Yes, it may be that you need to add this entry by hand.

Hmm, Alan Sewards says it is not necessary since the pointers are in the
recv-channels.ini file.

I don't dare to ask, who's right, but rather, what is recommended?


...

_____________________________________
[EUMETSAT Data Channel 2]
target_directory=F:&#92;received
tmp_directory=F:&#92;receiving&#92;tmp
_____________________________________


You are correct that with the data on different disks, one common entry in
recv.ini would not provide the best solution. By the way: I hope that is
two different physical disks, otherwise you will have the disk head madly
Yes, two drives, physically different. E: ist 250 GB, F: 400 GB.

I'll purge some 'e's from the temp-trm then and see...

Changing the architecture altogether could be one of the next steps.

The reason for coupling the temp and target files on the same disk / partition
was given here some years ago: That the files that would land in the target
directory in the end are composed piece by piece in the temp files, and that
moving them to the target then means just a change in the FAT. Isn't that
true any more on NTFS formatted disks (not sure to which generation this
old wisdom related).

Cheers,

U.
Ulrich

What I recommend is to # comment out the "tmp_directory" entry in recv.ini and use "tmp_directory" entries in recv-channels.ini only.

[EUMETSAT Data Channel 2]
target_directory=F:&#92;received
tmp_directory=F:&#92;receiving&#92;tmp

For the data that go to drive E: you use accordingly
...
tmp_directory=E:&#92;receiving&#92;tmp


Then you start end check whether these tmp_directories exist and work.

The files are assembled in the file on your ram-disk. Then they are written to the "tmp_directory". Finally they are moved out to the final position which is just a "rename" as long as the tmp_directory is on the same partition as the final "target" data directory. That's why you have to use at least 2 tmp_directories if you have 2 disks.

Hope this helps. And again, please try "tmp_directory" and not "temp_directory" ...

Cheers
Ernst

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Sun, 6 Mar 2011 17:29:20 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

Just to check, you /do/ have a tmp_directory entry in your
recv.ini:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive
directories?
How could this box run for years without the tmp definition in the
parameters 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.
Yes, it may be that you need to add this entry by hand.

Hmm, Alan Sewards says it is not necessary since the pointers are in the
recv-channels.ini file.

I don't dare to ask, who's right, but rather, what is recommended?


...

_____________________________________
[EUMETSAT Data Channel 2]
target_directory=F:&#92;received
tmp_directory=F:&#92;receiving&#92;tmp
_____________________________________


You are correct that with the data on different disks, one common entry in
recv.ini would not provide the best solution. By the way: I hope that is
two different physical disks, otherwise you will have the disk head madly
Yes, two drives, physically different. E: ist 250 GB, F: 400 GB.

I'll purge some 'e's from the temp-trm then and see...

Changing the architecture altogether could be one of the next steps.

The reason for coupling the temp and target files on the same disk / partition
was given here some years ago: That the files that would land in the target
directory in the end are composed piece by piece in the temp files, and that
moving them to the target then means just a change in the FAT. Isn't that
true any more on NTFS formatted disks (not sure to which generation this
old wisdom related).

Cheers,

U.

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: <MSG-1@...>
Von: "David J Taylor" <gm8arv@...>
Datum: Sun, 6 Mar 2011 17:29:20 -0000
Betreff: Re: [MSG-1] not yet perfect, but...
Antwort an: MSG-1@...

Just to check, you /do/ have a tmp_directory entry in your
recv.ini:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive
directories?
How could this box run for years without the tmp definition in the
parameters 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.
Yes, it may be that you need to add this entry by hand.

Hmm, Alan Sewards says it is not necessary since the pointers are in the
recv-channels.ini file.

I don't dare to ask, who's right, but rather, what is recommended?


...

_____________________________________
[EUMETSAT Data Channel 2]
target_directory=F:&#92;received
tmp_directory=F:&#92;receiving&#92;tmp
_____________________________________


You are correct that with the data on different disks, one common entry in
recv.ini would not provide the best solution. By the way: I hope that is
two different physical disks, otherwise you will have the disk head madly
Yes, two drives, physically different. E: ist 250 GB, F: 400 GB.


Cheers,

U.

Re: not yet perfect, but...

ernstlobsiger
 

--- In MSG-1@..., "Ulrich G. Kliegis" <Ulrich.Kliegis@...> wrote:



An: MSG-1@...
Von: "ernstlobsiger" <ernst.lobsiger@...>
Datum: Sun, 06 Mar 2011 16:13:27 -0000
Betreff: [MSG-1] Re: not yet perfect, but...
Antwort an: MSG-1@...

I think it should read "tmp_directory" instead of "temp_directory" in
recv-channels.ini.
Ernst,
danke für den Kommentar, but temp... seems to be the pregiven spelling in
the original sample, as I have it here.

Reducing the max rate to 20E6 did not change anything.

I also commented out EPS 5 temporarily - (almost) no effect. at least, in this
phase (about 15:50 UT) the rate of not-recovered packets grew.
Switching off a Dexatrek USB receiver (same as the world box) being
connected to a different PC two meters (about 6.7 ft) away, - no effect (I
suspected the open output socket, but it wasn't the culprit yet.) Connecting
the LNB cable shielding to a solid ground - nothing.

Ernst, the (temporary) temp_directory in recv.ini was derived from David's
question.

Alan, the board "looks good", no bad elcaps.

I feel a bit embarassed that just mine (out of millions of PCs running David's
software) makes such troubles. Hadn't I installed MRTG, everything would
look fine... :)

Cheers,
U.
Ulrich

When I google for "tmp_directory" or "temp_directory" and "recv.ini" I still beleive it should read "tmp_directory" ...

I looked up the proposal of a common "tmp_directory" under [parameters] in recv.ini on David's site. It seem possible but as you have the MSG1 and EPS data on different paritions or even Disks, this is really a bad idea. You must have the tmp_directory on the disk and partition where you finally put the data: As soon as a file is complete in the "tmp_directory" it will be moved to it's final place. If this is on the same partition only the "name" entry will be adjusted. If it's an another partition the whole data has to be recopied and the original data deleated. Not good ...

Hope this helps.

Ernst

Re: not yet perfect, but...

David J Taylor
 

David,
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:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive directories?
How could this box run for years without the tmp definition in the parameters
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.
Yes, it may be that you need to add this entry by hand.

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 one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added the tmp
pointer only minutes ago, being aware that it is only 21, half the truth... still
reflected in the missed packets rate.
[]
[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp
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...

U.
Ulrich, according to the 2.2.4a TelliCast Help information (viewed via the HTML shell), you need

tmp_directory=<directory>

So, for example:

_____________________________________
[EUMETSAT Data Channel 2]
target_directory=F:&#92;received
tmp_directory=F:&#92;receiving&#92;tmp
_____________________________________


You are correct that with the data on different disks, one common entry in recv.ini would not provide the best solution. By the way: I hope that is two different physical disks, otherwise you will have the disk head madly dashing between the two partitions on the one physical disk! Far better to have all the received data going to one partition, and the processed images on a /different/ physical disk. Can you not hear the noise the disk is making? <G> The hard disk of my receive-only PC is just 80GB.

Talking of recv.ini, it happens that mine has:

_____________________________________
[parameters]
file_delivery_speed=20000000
_____________________________________


So, broadly, I would have one large and one small HD, ~100GB for just the &#92;received&#92; directory tree, and 1-2TB for the processed and archived files. Topic for discussion - which HD should have the OS? I might suggest the small HD, but it would likely depend what else was on the system.

Thanks to the others for their input as well - Arne/Ernst's log file analysis program has help uncover anomalies in other areas. I'm sure that with Linux you also need to work out the data flow carefully for best results.

Cheers,
David
--
SatSignal software - quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@...

Re: not yet perfect, but...

Ulrich G. Kliegis
 

An: MSG-1@...
Von: "ernstlobsiger" <ernst.lobsiger@...>
Datum: Sun, 06 Mar 2011 16:13:27 -0000
Betreff: [MSG-1] Re: not yet perfect, but...
Antwort an: MSG-1@...

I think it should read "tmp_directory" instead of "temp_directory" in
recv-channels.ini.
Ernst,
danke für den Kommentar, but temp... seems to be the pregiven spelling in
the original sample, as I have it here.

Reducing the max rate to 20E6 did not change anything.

I also commented out EPS 5 temporarily - (almost) no effect. at least, in this
phase (about 15:50 UT) the rate of not-recovered packets grew.
Switching off a Dexatrek USB receiver (same as the world box) being
connected to a different PC two meters (about 6.7 ft) away, - no effect (I
suspected the open output socket, but it wasn't the culprit yet.) Connecting
the LNB cable shielding to a solid ground - nothing.

Ernst, the (temporary) temp_directory in recv.ini was derived from David's
question.

Alan, the board "looks good", no bad elcaps.

I feel a bit embarassed that just mine (out of millions of PCs running David's
software) makes such troubles. Hadn't I installed MRTG, everything would
look fine... :)

Cheers,
U.

Re: not yet perfect, but...

ernstlobsiger
 

--- In MSG-1@..., "Ulrich G. Kliegis" <Ulrich.Kliegis@...> wrote:


David,
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:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive directories?
How could this box run for years without the tmp definition in the parameters
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 one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added the tmp
pointer only minutes ago, being aware that it is only 21, half the truth... still
reflected in the missed packets rate.

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver Configuration File

# 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
#


[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx


[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?


[EOF]

[recv-channels.ini]
# recv-channels.ini - TelliCast+TelliVision Client channel configuration file
#
# 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=500
# 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=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# 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
# system.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp


[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]


target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

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...

U.
Hello Ullrich

I am far from my (Linux!) reception station and this is purely out of my head. Also the thread is pretty long by now. So for what it is worth:

a)
I think it should read "tmp_directory" instead of "temp_directory" in recv-channels.ini. Not sure the Tellicast Client understands both ...
b)
You have a very high file_delivery_speed in recv.ini. Default is 10000000 and I have never set it above 20000000 (on my old PCs).
c)
I don't understand the temp_directory under [parameters] in recv.ini.

Cheers
Ernst

Re: not yet perfect, but...

Ulrich G. Kliegis
 

I'm wondering whether the
cause of the loss is something not even associated with the PC, such
as some radio-frequency interference getting into the IF channel.
Perhaps something from the port at Kiel, just across from you? I
expect you have already made sure that the connectors are not loose.
David,
at the same time that I re-adjusted the EB9 LNB, I now also re-positioned
the LNBs for ASTRA and Hotbird. Although the receiver shows 98% signal
strength there and 92% quality (whatever that means) there are
someartifacts in the video image. But that may still be due to some position
error. I'll have to investigate that. The LNBs are phasically and galvanically
totaly separate for TV and Eumetcast, though. Just the cable shields meet
at some distinct earthing point.

I then suspected noise from a DECT phone nearby the dish. Switching it off
(completely) did not show any effect.

The dish does not point to the harboujr at all, and there is nothing in the
heighbourhood that could cause any interference.

At the moment, I feel a bit stranded.

Cheers,
U.

Re: not yet perfect, but...

James Brown
 

I don't suppose the issue of an incompatible motherboard is raising it's head here. It's just that I've never seen such a pattern of losses before.

Cheers
James
--
James Brown

Re: not yet perfect, but...

Alan Sewards
 

Ulrich,
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:

David,
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:
>
> _____________________________________
> [parameters]
> tmp_directory=temp
> _____________________________________
>
> pointing to the same partition as all the other receive directories?

How could this box run for years without the tmp definition in the
parameters
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
one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or
larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added
the tmp
pointer only minutes ago, being aware that it is only 21, half the
truth... still
reflected in the missed packets rate.

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver
Configuration File

# 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
#

[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx

[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?

[EOF]

[recv-channels.ini]
# recv-channels.ini - TelliCast+TelliVision Client channel configuration
file
#
# 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=500
# 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=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# 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
# system.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]

target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

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...

U.

--
Alan Sewards
email: alan@...
web site: http://asewards.free.fr

Re: not yet perfect, but...

Alan Banks <alan@...>
 

Hi Ulrich,
in my system Tellicast is on its own drive 'D'.
The tmp file is in the BusinessTV-IP folder and this is my Recv-channels.ini file


tmp_directory=tmp

[Info-Channel-1]
target_directory=D:&#92;dailylog

[Info-Channel-2]
target_directory=D:&#92;dailylog

[WWW-Channel]
target_directory=D:&#92;www&#92;eumetsat

[EUMETSAT Data Channel 1]
target_directory=D:&#92;received

[EUMETSAT Data Channel 2]
target_directory=D:&#92;received

[EUMETSAT Data Channel 3]
target_directory=D:&#92;received

[EUMETSAT Data Channel 4]
target_directory=D:&#92;received&#92;Data Channel 4

[EUMETSAT Data Channel 5]
target_directory=D:&#92;received-56

#[EUMETSAT Data Channel 6]
#target_directory=D:&#92;received-56

[EUMETSAT Data Channel 11]
target_directory=D:&#92;received

[EUMETSAT Data Channel 12]
target_directory=D:&#92;received

#[SAF-Europe]
#target_directory=D:&#92;received

#[SAF Europe]
#target_directory=D:&#92;received

[EPS-10]
target_directory=D:&#92;EPSreceived

#[EPS-4]
#target_directory=D:&#92;EPSreceived&#92;EPS4

#[EPS-13]
#target_directory=D:&#92;EPSreceived&#92;EPS13

[EPS-15]
target_directory=D:&#92;EPSreceived&#92;EPS15

#[EPS-16]
#target_directory=D:&#92;EPSreceived&#92;EPS16

#[EPS-17]
#target_directory=D:&#92;EPSreceived&#92;EPS17

[EPS-18]
target_directory=D:&#92;EPSreceived&#92;EPS18

[EPS-19]
target_directory=D:&#92;EPSreceived&#92;EPS19

Cheers

Alan

On 06/03/2011 14:16, Ulrich G. Kliegis wrote:

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver Configuration File

# 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
#


[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx


[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?


[EOF]

[recv-channels.ini]
# recv-channels.ini - TelliCast+TelliVision Client channel configuration file
#
# 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=500
# 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=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# 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
# system.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp


[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]


target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

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...

U.



------------------------------------

Unsure what a term means? Check the Glossary at:
http://www.satsignal.eu/wxsat/glossary.htm
Yahoo! Groups Links




Re: not yet perfect, but...

Ulrich G. Kliegis
 

David,
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:

_____________________________________
[parameters]
tmp_directory=temp
_____________________________________

pointing to the same partition as all the other receive directories?
How could this box run for years without the tmp definition in the parameters
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 one
partition but will be shifted to the other later on.

Alternatively, I could bring both together now on a single terabyte or larger
disk. What has more advantages?

This is the content of the present recv.ini file, and note that I added the tmp
pointer only minutes ago, being aware that it is only 21, half the truth... still
reflected in the missed packets rate.

[recv.ini]
# recv.ini - TelliNet+TelliCast+TelliVision: central Receiver Configuration File

# 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
#


[recipient]
user_name=UlrichKliegis
user_key_crypt= xxxxxxxxxxxxxxxx


[shell]
login=none
port=2517
refresh=3

[watchdog]
#error_script=none./error.sh
#error_script_cause_announcement=30

[logging]
log_file_size=1000000
log_file_number=2
log_level=quiet

[locations]
file_database_directory=R:&#92;receiving&#92;tmp
log_file=>>recv.log
license_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;license.ini
channels_file=C:&#92;Programme&#92;T-Systems&#92;BusinessTV-IP&#92;recv-channels.ini

[announcement_channel]
address=224.223.222.223:4711
name=TSL Announcement Channel

[parameters]
interface_address=192.168.238.238
file_database_size=325000000
#file_delivery_counter=50
file_delivery_speed=50000000
temp_directory=E:&#92;receiving&#92;tmp
# the previous line added 2011-03-06 - or should this point to R: too?


[EOF]

[recv-channels.ini]
# recv-channels.ini - TelliCast+TelliVision Client channel configuration file
#
# 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=500
# 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=F:&#92;received
# target_directory: directory for received files.
# The target_directory name is relative to the current
# working
# directory.
# (default: ./received)

# allow_execute=1
# allow_execute: 1=allow execution of programs/scripts after job
# reception if specified within the sender job file
# (default: 0=not allowed)

temp_directory=F:&#92;receiving&#92;tmp
# 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
# system.
# (default: undefined=off
# but default value may be redefined in recv.ini)

[EUMETSAT Data Channel 2]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp


[EUMETSAT Data Channel 3]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 4]


target_directory=F:&#92;received&#92;Data Channel 4

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 5]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EUMETSAT Data Channel 6]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[Americas-CH1]

target_directory=F:&#92;Americas-CH1

temp_directory=F:&#92;receiving&#92;tmp

[EPS-1]

target_directory=E:&#92;EPS&#92;EPS-1

temp_directory=E:&#92;receiving&#92;tmp

[EPS-2]

target_directory=E:&#92;EPS&#92;EPS-2

temp_directory=E:&#92;receiving&#92;tmp

[EPS-3]

target_directory=E:&#92;EPS&#92;EPS-3

temp_directory=E:&#92;receiving&#92;tmp

[EPS-4]

target_directory=E:&#92;EPS&#92;EPS-4

temp_directory=E:&#92;receiving&#92;tmp

[EPS-5]

target_directory=E:&#92;EPS&#92;EPS-5

temp_directory=E:&#92;receiving&#92;tmp

[EPS-6]

target_directory=E:&#92;EPS&#92;EPS-6

temp_directory=E:&#92;receiving&#92;tmp

[EPS-7]

target_directory=E:&#92;EPS&#92;EPS-7

temp_directory=E:&#92;receiving&#92;tmp

[EPS-8]

target_directory=E:&#92;EPS&#92;EPS-8

temp_directory=E:&#92;receiving&#92;tmp

[EPS-9]

target_directory=E:&#92;EPS&#92;EPS-9

temp_directory=E:&#92;receiving&#92;tmp

[EPS-10]

target_directory=E:&#92;EPS&#92;EPS-10

temp_directory=E:&#92;receiving&#92;tmp

[EPS-11]

target_directory=E:&#92;EPS&#92;EPS-11

temp_directory=E:&#92;receiving&#92;tmp

[EPS-12]

target_directory=E:&#92;EPS&#92;EPS-12

temp_directory=E:&#92;receiving&#92;tmp

[EPS-13]

target_directory=E:&#92;EPS&#92;EPS-13

temp_directory=E:&#92;receiving&#92;tmp

[EPS-14]

target_directory=E:&#92;EPS&#92;EPS-14

temp_directory=E:&#92;receiving&#92;tmp

[EPS-15]

target_directory=E:&#92;EPS&#92;EPS-15

temp_directory=E:&#92;receiving&#92;tmp

[EPS-16]

target_directory=E:&#92;EPS&#92;EPS-16

temp_directory=E:&#92;receiving&#92;tmp

[EPS-17]

target_directory=E:&#92;EPS&#92;EPS-17

temp_directory=E:&#92;receiving&#92;tmp

[EPS-18]

target_directory=E:&#92;EPS&#92;EPS-18

temp_directory=E:&#92;receiving&#92;tmp

[DWDSAT]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[SAF-Europe]

target_directory=F:&#92;received

temp_directory=F:&#92;receiving&#92;tmp

[EOF]

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...

U.