Hi, Andreas!

Вторник Январь 06 2004, at 00:47 Andreas Mayer wrote to All:

 AM> I've got a problem with HTick and some TIC-Files containing a
 AM> Destination Line that is not addressed to my system. HTick reports an
 AM> error and changes the *.tic to a *.ntu file. The uplink where I
 AM> received this TIC from told me that his ticker doesn't support this
 AM> keyword at all and therefore leaves the line as it is which originally
 AM> came from his uplink. Is there an option in HTick to just ignore this
 AM> keyword instead of getting an error?

No, htick doesn't support this. In future we are going to make perl hooks
which will give ability to fix this. Now you can do the following:
in your mailer write a hook after receiving tic file from that node. There
you can place script which will fix this.
For example in binkd:

exec /path/to/tic_fix *F *A0

/path/to/tic_fix:
#!/usr/bin/perl

open(F, "$ARGV[0]) || die "Can't open $ARGV[0]\n";
open(FOUT, "$ARGV[0].tmp) || die "Can't open $ARGV[0].tmp\n";
while($line=)
{
    chomp($line);
    $line =~ s/^TO:\s+(\d+:\d+\/\d+).*/TO: 2:464/910/i;
    print FOUT "$line\n";
}
close(F);
close(FOUT);
rename($ARGV[0].tmp, $ARGV[0]);


Something like that.

    Dmitry

--- GoldED+/LNX 1.1.5