![]() So he flicked off the power switch on the system. He figured if it worked for his computer, it would work for this one, too. He realized that when he turned off his computer at home and turned it back on, that seemed to cure almost all problems. They didn't want to risk the wrath of their boss. They pressured him more - they just couldn't wait 45 minutes. He left a message and went to update the office admins. Herman called me, but I was out of the office for about 45 minutes (this was in the days before cell phones and pagers). Instead, he told his programmer that he should place a call to me to get help. ![]() Somehow he had forgotten the cheat sheet I had left him that told him how to identify and kill a process. ![]() Somehow he had forgotten that there were 15 terminals scattered around the office. Somehow, Dwayne had forgotten that the console had 12 distinct sessions and all he had to do was have the office admins Alt-F key to a different screen. who had been given more extensive training by necessity, even if he didn't want to learn it. The office admins put pressure on him to do something, so he called Dwayne. Dwayne hadn't thought it was important for Herman to have anything but user training for Xenix, so he couldn't really do much. ![]() Their boss was exceptionally impatient and demanding, so they wanted to know what Herman could do to help them. They told him that the system was locked up and that they couldn't continue their data entry. [Ever worked with a technology that seemed to defy all logic or simply drove you up the wall? Submit your story to four weeks after the system was up and running, Herman was on-site doing some coding and the two office admins came into his office. Dwayne, who was running behind on his schedule to get the application done and fully taking advantage of the multi-user system, hired Herman, a college student, to do some coding for him. The application had been written by a local consultant - let's call him Dwayne - who knew FoxBASE in single-user mode on DOS but didn't know Xenix and didn't really want to. We had a client that purchased a 286-based server running SCO Xenix to run a FoxBASE application in a multi-user environment. The help command is man's best friend (not dogs).Lack of knowledge + heat of the moment = bad decisions I started in the industry in the early eighties and worked as a technical salesperson for a local micro-computer company. Sure! Roles are remembered by ID, so changing the name and color shouldn't affect performance. No, kicking/banning Gaius will never reset your settings or prefix. This is because there were 10 people who joined the server with less than 12 seconds between each join. If one troll joins the server, and then another troll joins after 2 seconds, the number is 2, then 8 more join in less than 5 seconds between each join, the number jumps to 10, and causes Gaius to trigger the automated panic in the server. If 12 seconds pass and no one else joined after Josh, then the number goes back to 0. If Josh (2) joins 6 seconds after John (1), the number is 2. So the triggered number is staying at one. If 12 seconds has passed by and John joins at 13 seconds after Sarah (1), then Sarah is no longer counted, and John becomes 1. If Sarah (1) joins the server, the number becomes 1. To help clarify this, let's consider users to simply be a number, only a number. The time is not based on only the first person who joined it is based on the previous person who joined the server. If we were to say 10 people must join the server within 12 seconds, then that would be incorrect. Using the example above, the users is set to 10 and the seconds is set to 12. What Do the Numbers in the Last Two Rows Above Mean? This feature for is reserved for Gaius Plus only. Sets the number of seconds needed between joins to increase the trigger number This feature is reserved for Gaius Plus only. Sets the number of server joins required to trigger panic mode Displays the current panic mode settings Gaius has to have Manage Roles permission or else panic mode will not work. Configuring the settings for users and settings in the command is currently only available for Gaius Plus users. Communities with higher traffic might need to have a more relaxed system to better detect anomalies, while slower moving servers can use the stricter settings. Premium users have the freedom to make it as strict as allowable or a relaxed as allowable to use what fits best for their community. This is the only command for the panic mode function. This is a fairly simple and straightforward tool that helps monitor and detect raids to your configurations and takes action upon panic mode being triggered. There is only one command to the panic mode feature. The configuration features for automated panic mode is reserved for Gaius Plus only.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |