Shell Scripts>

#167453 49 Wed Sep 28 09:02:25 1994 Stone @
3
aThe Ghetto
0,
3N. Seattle
0,
3
aJack's Basement
0
The Raft has a program that will let you send AT commands from DOS. Maybe that would help you.
#167454 49 Thu Sep 29 01:23:14 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
#USERAPP "twit's 'nym" "tosshim.bat" where tosshim.bat is "ECHO ATH > COMPORT" Or somthing along that line. Wolfie's is more elegant, though.
#168456 54 Sun Oct 2 13:29:11 1994 Lab Rat @ The Laboratory, Seattle
Alpha Wolf> if you use the #ADD function, it puts the result in _RESULT. So therefore #ADD _FOOVAR 1 #ASGN _RESULT _FOOVAR increments _FOOVAR by one. can't use just #ADD _FOOVAR 1
#170065 54 Fri Oct 7 23:05:31 1994 Alpha Wolf @ The Raft, Seattle, WA, US
right, overcommented... besides, i usually delete all the coments right befor e i put it online... runs faster... >:) hmm... actually, what if one has accounting disabled and you set the credits to 0? does it kick them off, or ignore it completely? echo ath0 > com2 heh... i like that idea... actually... you could have some real fun with another group.... Hmm.. how to kick someone off for the rest of the day... maybe a group, a date-check... hmm.. scuse me, i'm going to go try something.. :)
#171475 54 Tue Oct 11 21:38:46 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Wow. Serious NetLag.
#171711 54 Thu Oct 13 22:48:42 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Your reply (8 days after my entry) arrived here in 4. 12 day turnaround. It'll shorten up considerably, very soon (this weekend). Accounting disabled prevents timeout of the user, so setting time to 0 would have no effect at all. You should be able to set the accounting status from script, though...
#171712 54 Thu Oct 13 22:50:08 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Maybe not... Nothing in the Docs.
#172121 54 Sat Oct 15 14:21:49 1994 Alpha Wolf @ The Raft, Seattle, WA, US
accounting for a user? hmm... if you set it to 1 and kick them off, they call back up... they are off for the day, right?? hmm... more work to be done...
#172566 54 Sun Oct 16 19:57:10 1994 Lab Rat @ The Laboratory, Seattle
Alpha > I assume your latest post is referring to an accounting-enabled environment. in which case no they would be on briefly, kicked off, and then if they went away for a while they might even stay on for five or ten minutes. Because citadel uses a continuously incrementing accounting refresh system. so if you wanted them off for a while you'd have to set their accounting to -30 or something.
#172449 54 Sun Oct 16 21:44:23 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Yup. It gives 'em 60 seconds to say good-bye, and won't let them back in 'til midnight + a few seconds...
#172756 54 Mon Oct 17 01:43:52 1994 Alpha Wolf @ Memory Alpha, Kent, U.S.A.
Lab Rat: Ah, so you can set the users time as negative... >:) hmm... does the accounting refresh itself at midnight? (or at least every 24 hours???)
#172755 54 Mon Oct 17 11:06:29 1994 [
3
fI'm back as
0] Black Wolf [
3
eSir Rolfsalot....
0] @ Line NoiZe, Ferndale, U.S.A.
hmm
#172955 54 Mon Oct 17 19:07:10 1994 Lab Rat @ The Laboratory, Seattle
Uh Monty, no. Citadel does a continuous refresh. I'm not sure how the exact algorithm works (you'd have to talk to brent) but say if you are kicked off with zero minutes, if you wait like an hour or so and log back in, you'll have say 5 minutes in your account. And if you wait several hours, it will refresh your account back to the original level, at which point it will stop. actually I want to know what the algorithm is. BRENT > TELL US WHAT THE ACCOUNTING REFRESH ALGORITHM IS!!!!!!!!
#172956 54 Mon Oct 17 20:58:17 1994 Alpha Wolf @ Memory Alpha, Kent, U.S.A.
>>>>:)
#173635 54 Tue Oct 18 22:20:10 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
So much for that idea... Back to setting it to negative time. So, on login, Cit checks the logout time of the previous connect, and adds a proportional amount of the daily increment, up to the maximum?
#173818 54 Wed Oct 19 08:19:14 1994 Lab Rat @ The Laboratory, sea
Monty > not the logout time, no. it keeps a running total of your current time allowed. but the rest is exactly on.
#174039 54 Wed Oct 19 23:13:40 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Constantly updating _every_ user's time? Eeek. What a method.
#174222 54 Thu Oct 20 11:10:33 1994 Lab Rat @ The Laboratory, Seattle
Monty > No, of course not! It updates it when next you log on. But to the user it appears the cit has been keeping track the whole time he's been off.
#174373 54 Thu Oct 20 23:24:32 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
What I posted at the end of Oct 18th...
#175573 54 Sat Oct 22 04:13:25 1994 Richard Goldfinder @ The Raft, Seattle, WA, US
Geez... it uses the values in GRPDATA.CIT to figure out what your balance should be. It multiplies the number of days and partial days by #DAY_INC for the value. The days it just straight multiplies, the seconds it multiplies by #DAY_INC then divides by 86400 (60*60*24). If the amount of time from your last call is negative, it gives you a day's worth of credits for the sysop's mistake in bad timekeeping. It then takes the lesser of that value and #MAX_BAL, and that's your number of credits. There's no doubt in my mind that Lab Rat is referring to the seconds when he refers to continuous refresh. Not exactly continuous, since it's by the second, but probably close enough.
#175574 54 Sat Oct 22 20:29:42 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Yo, Richard... continuous refresh... &)
#175801 54 Sun Oct 23 02:15:21 1994 Lab Rat @ The Laboratory, Seattle
Rich > yeah, by continuous refresh I am referring to the seconds bit. just a bad choice of words on my part, or perhaps my mind is warped; or maybe I'm confused and lost because someone stole my brain a few days ago. but you should take out the code for giving a day's worth of credits for negative accounting; if people download a single file that takes, say, three or four hours, and you normally get sixty minutes a day, I don't (or should say wouldn't) want that user to be able to log in again until he had waited the full two or three days... or am I misunderstanding something?
#176926 54 Sun Oct 23 06:47:51 1994 Richard Goldfinder @ The Raft, Seattle, WA, US
I guess I wasn't adequately clear above. When I said "If the amount of time from your last call is negative", I meant the amount of time that had transpired, not the number of credits in the account. For example, several people get confused about the current year in the first week of January. If one call you logged in 1/1/95 and the next call you logged in on 1/5/94, rather than giving you a huge number of negative credits (because the number of days transpired is negative), it'll give you a day's worth (for the sysop's mistake in bad timekeeping). Of course, when the sysop sets the clock properly and you call again on 1/9/95, the system will think it's been over a year since you called last and you'll probably end up with quite a load of credits, so we don't worry about that.
#176925 54 Sun Oct 23 11:48:42 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Good point, lr... Sysop's 'bad timekeeping', indeed. I'd much prefer to keep the *.* dl'er honest, and hold him off for the time he used.
#176977 54 Sun Oct 23 23:55:17 1994 Lab Rat @ The Laboratory, sea
richard > ah! thanks for the clarification. don't you hate it when you're so tired that you can feel the room spinning mildly... or maybe that is just my rollie-chair...
#176724 54 Tue Oct 25 03:57:03 1994 MontyL @ Black Mountain, Kendall, US/WA/Whatcom
Check your wheels, lr... Much more sense the second time around, Richard. Thanks!
Shell Scripts> _