Process Scheduling with Timeout/Watch in Debian 6.x

The commands timeout and watch are great tools to have for reliable, on-the-fly process scheduling; especially in cases where cron isn't working properly and fixing it would take too long. I've included short descriptions of both commands and an example for you to play with.

The command timeout runs a process (command or script) for a period of time, when time runs out the command timeout sends the signal you specified to the process, and if the process is still running after a period of time the command timeout will send the process a KILL signal. The command timeout accepts intervals of seconds (s), minutes (m), hours (h) and days (d), for its period of time. The command timeout accepts all of the signals accepted by the command kill for its signal argument. Here's its command syntax:

timeout -s <signal> -k <time with suffix> <duration> <process> <process arguments>

The command watch periodically runs a process (command or script) for a period of seconds then displays the output of the process fullscreen, so that, the user can watch for differences. The command watch has interesting options for running processes at precise times and for dealing with exit errors from processes. When specifying the process for the command watch to run the process and its arguments have to enclosed in single quotes or double quotes. Here's its command syntax:

watch -n <interval of seconds> <process with arguments>

For example, in my post titled "TCP/UDP Whitelist Connection Script," I mentioned using cron to run the bash script "whitelist.sh" every couple of minutes to close active TCP/UDP servers and connections unknown to the user. Instead of playing with cron you could tell the command timeout to run watch and watch to run the bash script "whitelist.sh". In this example, I'm telling the command timeout to send the process watch the KILL signal after 4 hours, and if the process watch is still running after 245 minutes then send it another KILL signal. I'm also telling the command watch to run the bash script "whitelist.sh" located in my home directory every 120 seconds (or 2 minutes). Here's the comand to run:

timeout -s SIGKILL -k 245m 4h watch -n 120 /home/username/whitelist.sh

Do you have a suggestion about how to improve this blog? Let's talk about it. Contact me at David.Brenner.Jr@Gmail.com or 720-584-5229.

Comments

The meaning of time in reinforcement learning

Reinforcement learning (RL) is one of three basic machine learning paradigms, alongside supervised learning and unsupervised learning. Reinforcement learning is concerned with how software agents ought to take actions in an environment in order to maximize the notion of cumulative reward through the process of trial and error. In reinforcement learning an agent starts at an empty state then analyzes the available datasets according to a policy of positive states and negative states. Rather than being explicitly taught as in supervised learning the correct set of actions for performing a task, reinforcement learning uses rewards as signals for positive states and punishments as signals for negative states. The agent obtains the best path to a desirable reward as a cumulation of positive states and negative states. As compared to unsupervised learning, reinforcement learning is different in terms of goals. While the goal in unsupervised learning is to find similarities and differences...

Threat detection of zero-day attacks in Linux with Python

You can investigate suspicious activity that could be a zero-day attack by collecting relevant machine data from your endpoint. You can use the machine data to create your own analysis. Before you start your investigation you will need to determine normal activity on your endpoint. Normal activity is the scope of functionality of the software on your endpoint during periods of low activity and high activity. You will need some kind of software that periodically collects specific machine data from your endpoint like my software developed in Python that's available for free download at https://github.com/davidbrennerjr/server-stats-collector Ingest one or more of the following machine data: General system-wide error messages from /var/log/syslog Auditing logs of application rulesets Auditing logs of security contexts Auditing logs of login attempts from /var/log/auth.log Auditing logs of user management or group manageme...

Web app comparison of async and real-time

Advantages of asynchronous web apps Generic request/response structure Stateless session control Message queue management Token access based on serverside date-time format PostgreSQL paging using token-centric tables and functions Shared pools of resources per customer One-to-many security policies Single domain name with TLS cert over HTTPS Shared bandwidth for uploads/downloads No endpoint/device registration No direct access to server resources Web app aggregation as control panel A/B Testing Advantages of (near) real-time web apps Stateful session control On-demand communication protocols per customer Custom request/response structure per customer Custom date-time formats per customer Endpoint/device registration PostgreSQL paging using static tables and aggregate functions Immediate execution of requests Dedicated pools of resources per customer Dedicated TLS cert over HTTPS per customer Dedicated IP addres...

David Brenner Jr

Search This Blog