| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | echotoss.log |
On Feb 15 15:21 96, Bill Bond of 1:325/118.1 wrote to jim barchuk: jb>> The deal is that right now the -only- reason I have to exit jb>> msged -is- to create echotoss.log. If I could do that on jb>> the fly I'd -never- have to exit. :) BB> So if it wrote it on the fly, automatically, that would be ok? What's the down side? How harmful are duplicate entries in echotoss.log? jb>> Here's another trick: how about re-reading msged.cfg -while- jb>> it's running? BB> Groan :) Just say no. What he really wants is a full msged.cfg editor built in; not a bad idea, but a fair size job. Jerry Schwartz @EOT: --- MsgedSQB 3.30.01* Origin: Write by Night (1:142/928) SEEN-BY: 50/99 78/0 270/101 640/101 201 206 217 232 233 238 302 305 370 531 SEEN-BY: 640/820 821 822 823 690/660 711/401 409 413 420 423 430 808 809 924 SEEN-BY: 711/934 713/888 714/906 800/1 7877/2809 @PATH: 142/928 1 3615/50 396/1 270/101 640/201 820 711/409 413 808 809 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™.