home *** CD-ROM | disk | FTP | other *** search
- ; =============================================================================
- ; XENIA.EVT Event file Xenia Version 1.98 - January 1995
- ; =============================================================================
- ; This file is read by Xenia, do *NOT* INCLUDE it into the main config!
- ;
- ; You can have a separate event file for a specific Xenia task.
- ; Create XENIA1.EVT for task 1, XENIA99.EVT for task 99, and so on.
- ; You can then still use this XENIA.EVT as an easy default for other tasks.
- ;
- ; IMPORTANT NOTE!
- ; Only modify a XENIA*.EVT file while Xenia tasks that use it are NOT running.
- ; Xenia uses timestamp comparison between XENIA*.SCD and XENIA*.EVT to detect
- ; whether the schedule has changed, and stamps XENIA*.SCD with the XENIA*.EVT
- ; time on exit.
- ;
- ; BTW: I know the scheduler sucks, a completely new design is on its way.....
-
-
- ; -----------------------------------------------------------------------------
- ; Basic format of an event line:
- ; Tag Days StartTime [EndTime] [Options]
-
- ; Tag Xn Exit at start of event with errorlevel n.
- ; A-W Schedule tag, exit with errorlevel 4 at start of event so you
- ; can get your mail packed or create polls.
- ; If you have configured the 'MAILPACK <cmdstring>' statement,
- ; that command is executed INSTEAD of the errorlevel exit.
- ; Two parameters are passed: the task number and the schedule tag.
- ; Z Don't exit but just set some behaviour options.
-
-
- ; Some errorlevels are already in use by Xenia:
- ;
- ; 0 No error, normal termination of Xenia (Alt-X, SHUTDOWN.## semaphore)
- ; 1 Fatal dos error, restart Xenia
- ; 2 Internal error, probably bug in program
- ; 3 Default for APPERRORLEVEL if EXTAPP method BATCH is used
- ; 4 See A-W schedule tag info above
- ; 5-8 Not used but reserved for Xenia internal
- ; If EXTAPP method EXIT is used, Xenia will exit with the an errorlevel equal
- ; to connectspeed/100 (modulo 256 under DOS)
- ; Other errorlevels may be used freely in events or APPKEY statements
-
-
- ; Days Specify which days of the week the event should be active
- ; Sun,Mon,Tue,Wed,Thu,Fri,Sat; special: Week,WkEnd,All
- ; To combine days, add them with + (ie. Week+Sat, Tue+Fri)
-
-
- ; Starttime & Endtime
- ; hh:mm Military format, ie hours 00-24, minutes 00-59
- ; If no endtime is specified, the event will be 60 minutes long
- ; Only ONE event can be active at any time, so overlapping is only useful if
- ; you use for instance the D)ynamic option. Otherwise it's not even allowed.
- ; Events can't wrap through midnight either.
-
-
- ; Options (first letter is enough)
- ; B)BS EXTAPP BBS allowed, for users calling in with a terminal.
- ; F)orced Also start if Xenia was start PAST original event end-time.
- ; N)o-requests Still accepted, but response-msg will explain to caller.
- ; C)M/Crash Only initiate calls for immediate/crash mail, no normal stuff.
- ; #)MailHour Allowed to call non-CM nodes.
- ; H)iPriCrash Call out for CrashMail no matter cost or (lack of) CM flag.
- ; Q)ueue=nnnn Only call out if amount of mail >nnnnKB
- ; D)ynamic End event if no more calls to make (mail in outbound).
- ; E)xit-dynamic Exit Xenia if no more polls to make (used by Xenia Point)
- ; R)eceive-only Don't call out for any mail, not even immediate/crash
- ; S)end-only Don't answer any inbound calls (ie. ignore RING signals)
- ; M)ail=norm[,arc[,fax]] Errorlevel for exit when normal/arcmail/fax received
- ; The arc and fax parms are optional, default to same as normal.
- ; If a tasknumber was specified, and all settings are 0, a file
- ; called MAILFLAG.## is created instead (## is task nr. in hex).
- ; Can be used as semaphore for a separate mail handling process.
- ; If all settings are 0 but statement MAILPROCESS <cmdstring>
- ; has been configured, that command is executed instead of
- ; creating the semaphore file....
- ; A)vgwait=n Average no. seconds wait between making calls (min=0, max=240)
- ; Xenia will wait a random time, between -50% and +50% of avg.
- ; T)ry=con,noc Retry counter limits for failed-connects,no-connect
- ; (connect min=0,max=9 noconnect min=0,max=32000)
- ; Value of 0 means ENDLESS, no limit to that number of tries!!!!
- ; Z)ero-counters Delete/zero the *.$$# retry counter files at start of event.
- ; Only applies to the noconnect counters, not the connect count
- ; for failed mailsessions....
-
- ; -----------------------------------------------------------------------------
- z All 00:00 04:30 B A=240 T=2,0
- ; Zone 2 ZMH 02:30-03:30 UTC (03:30-04:30 CET, 04:30-05:30 daylight savings)
- ; Just disable BBS; no # flag need, MAILHOUR in XENSYS.CFG takes care of that.
- z All 04:30 05:30 A=240 T=2,0
- z All 05:30 08:00 B A=240 T=2,0
- z Week 08:00 18:00 C B A=240 T=2,0
- z WkEnd 08:00 18:00 B A=240 T=2,0
- z All 18:00 24:00 B A=240 T=2,0
-
- ;z All 00:00 02:30 C B m=100 ; 1 BBS
- ;x20 All 02:30 03:30 Z T=2,6 # C A=120 B m=100 ; 2 BBS Natl Poll
- ;z All 03:30 04:30 R N m=100 ; 3 ZMH
- ;z All 04:30 05:30 R B m=100 ; 4 BBS winter
- ;x20 All 05:30 06:30 T=1,2 # C A=120 B m=100 ; 5 BBS Intl Poll
- ;z All 06:30 08:30 R B m=100 ; 6 BBS
- ;x110 Sat 08:30 08:35 R S m=100 ; 7 Weekly Maintainance
- ;x111 Sun+Week 08:30 08:35 R S m=100 ; 8 Daily
- ;z All 08:35 22:00 C S R m=100 ; 9 day
- ;z All 22:00 23:00 C A=120 S m=100 ; 10 day
- ;z All 23:00 24:00 R B m=100 ; 11 day
-
-
- ; =============================================================================