Hello Russell!

11 Oct 2010 17:37, Russell Tiedt wrote to All:

 RT> It has been a long, long time, since I last setup a Husky system, and 
 RT> then I used a rather simple config file ...

as me just using /home/xpoint/fido/config/config

 RT> Now I am working from the sample config file ....

yep more samples make it works worse sometimes :)

 RT> Using the keywords
 RT> AutoAreaCreateFile [fidoconfigdir]echoareas

this will soon mess it up for you i belive, better is to keep all static
setting first in config file and then let husky add dynamic in the end of
config, the dynamic config lines can be sorted with mcedit just fine

 RT> Echo areas are added to this file when auto created ...

yes that option is fine for what it should do

 RT> Is it possible to have Msged read/use this file for it config.

yes, i post my whole msged.cfg to show how:

   ----- msged.cfg begins -----
AreafileFlags 8
Areafile Fidoconfig Both
Readmap /home/xpoint/fido/config/readmaps.dat
Writemap /home/xpoint/fido/config/writmaps.dat
OutputCharset LATIN-1
AssumeCharset CP1125
Helpfile /home/xpoint/fido/config/msghelp.dat
Template /home/xpoint/fido/config/msged.tpl
Template /home/xpoint/fido/config/msged-dk.tpl
Template /home/xpoint/fido/config/msged-de.tpl
Template /home/xpoint/fido/config/msged-se.tpl
include /home/xpoint/fido/config/scheme.004
SortAreas G
Alias pavel "Pavel A. Pribitkin" 2:5030/786.0 p "Hi Pavel"

RobotName Areafix
RobotName Filefix
RobotName filemgr
RobotName areamgr
;
; 0 international
; 1 dansk
; 2 german
; 3 svensk
;
GroupSettings "FIDO" 0 0
GroupSettings "KOFO" 0 0
GroupSettings "NORD" 1 1
GroupSettings "R20" 3 3
GroupSettings "R21" 3 3
GroupSettings "R23" 1 1
GroupSettings "R24" 2 2
GroupSettings "R50" 0 0
GroupSettings "WARD" 0 0
GroupSettings "XPOINT" 0 0
GroupSettings "Z39" 0 0

Origin www.region23.dk/ www.fido.dk/ <128000K ram after bootup

IF TERM=linux
     Switch colors on
     Switch BS127 on
     Switch pseudographics off
ELIF TERM=cons25
     Switch colors on
     Switch BS127 off
     Switch pseudographics off
ELIF TERM=vt220
     Switch colors on
     Switch BS127 off
     Switch pseudographics off
ELIF TERM=xterm
     Switch colors on
     Switch BS127 on
     Switch pseudographics on
ELIF TERM=ansi
     Switch colors on
     Switch BS127 off
     Switch pseudographics on
ELSE
     Switch colors off
     Switch BS127 off
     Switch pseudographics off
ENDIF
Quote _&>_
QuoteRight 76
Switch EditOriginLines off
Switch EditTearLines off
Switch HardQuote on
Switch UseMouse Off
Switch XXLTearline on
Switch NetmailVia off
Switch ShowAddr off
EnableSC
Function 0 ^M \0x1f00
Function 1 \0x23
Scan
UserOffset 0
FreqArea NetmailArea
NodePath /home/xpoint/fido/nodelist/v7
nodelist fidonet NODEX SYSOP.ndx
UserList /home/xpoint/fido/nodelist/userlist
Gate Domains
   ----- msged.cfg ends -----

the 2 first lines is what does it :=)

but you need msged compile so ldd gives

type pavel in msged writes hi pavel in subject, funny way of remember node
number and subject with msged, extend it to your uplink passwords is
usefull

   ----- msged.ldd begins -----
linux-gate.so.1 =>  (0xffffe000)
libfidoconfig.so.1.4 => /home/xpoint/fido/lib/libfidoconfig.so.1.4 (0x37792000)
 libsmapi.so.2.4 => /home/xpoint/fido/lib/libsmapi.so.2.4 (0x37779000)
 libncurses.so.5 => /lib/libncurses.so.5 (0x37735000)
 libc.so.6 => /lib/libc.so.6 (0x375ef000)
 libdl.so.2 => /lib/libdl.so.2 (0x375ea000)
 /lib/ld-linux.so.2 (0x377c3000)
   ----- msged.ldd ends -----
 
 RT> Is there a keyword, to have MSGED read this file instead of appending 
 RT> it's contents to the msged.cfg file?

yes if tparser gives all echoarea in the list see my first 2 lines in msged.cfg

 RT> Next ... I used to use the route keyword as follows ...

 RT> route crash 1:140/1 1:* 3:* 4:*
 RT> route crash 2:292/285 2:*

 RT> but tparser does not show routing information, when I use this format 

hmm this should work

 RT> Also I want to route all mail for zone 1 via 1:140/1 EXCEPT mail for 
 RT> nodes who get their feed from 1:3634/12

 RT> route 1:140/1 1:*
 RT> route 1:3634/12 1:3634/*

then swap this 2 lines, route is topdown order in husky first match wins :)

 RT> Is the order of these statement reguired to be in any special order 
 RT> for this to work or not ...

yes order is important :)

 RT> Many thanks,

no problem, btw see the fconf2* in fidoconf to export configs to your non
husky programs such as golded :)


 Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/2.6.34-gentoo-r6 (i686))