| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Event problem |
Hi Joe, Joe Negron wrote in a message to Richard Webb... RW> [...] If you don't want your 23:59event missed, move your other > event to 23:59 for end time, and start your forced maint event > at 00:00, and it'll run no matter what. JN> Well, that would require some re-working of my batch files (which use JN> internal 4OS2 functions to rename the log files according to the JN> date), but it's doable. Thanks. I do that on my system, as well as on my boss node. I did, however, move the maintenance stuff on the boss node to 05:00 a.m. because we're popular around midnight, it seems. We defrag, etc, as well as name logs according to date, generate reports with binkla which are Then sent to all sysops, etc. Be sure that the event before your 23:59 event is changed to reflect that itstops at 24:00, or you'll have a problem, but then start your maint event at 00:00 and it'll run as you wish, just make it a forced event as it was before. Regards, Richard ... Any IC protected by a fast acting fuse will protect the fuse by blowing first. --- PPoint 2.00* Origin: Electric Spider Productions (1:283/525.5) SEEN-BY: 50/99 157/534 620/243 622/419 623/630 625/100 626/660 665 667 668 SEEN-BY: 626/670 633/2 640/820 711/401 409 410 413 416 430 501 808 809 934 SEEN-BY: 711/955 712/515 713/888 714/906 800/1 @PATH: 283/525 121 270/101 396/1 157/110 534 626/660 711/401 808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.