Timeout on a script or program in Linux is easy! Did you ever have the need to kill a process if it takes too long to run for any reason? Then this post will show you how you do just that.
This could be used to prevent a cronjob for running too long or prevent cronjobs from overlapping if a lock-file is not the optimal solution in your case. It could also be used in a case where a process freezes for unknown reasons, and you need to force a restart of it based on a how long it has been running for.
This is not just useful for cronjobs, it can set a timeout on any process, script or program you run!
You may have experienced it before, you create a cronjob to change some data every X hour or minutes and one day this job takes longer than it usually does and cron spawns another job before the first one is finished.
This can result in data corruption or deletion of data that should not have been deleted, all depending on what the cronjob is set up to do
To prevent bad things from happening, a good rule of thumb is to always use a lockfile
A lockfile is a small file, it virtually takes up no space, at least so little you won’t care (The actual size depends on your filesystem). Sometimes it contains a PID, sometimes a timestamp or just plain empty. Depending on how the lockfile is managed Continue reading →
Today I had to run a script on a 64Bit server, but was met with the following error:
/lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Reason for the /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory error
The /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory error will happen only on 64 bit systems, the cause is the that 32 bit libraries are missing from the system and the script/program needs them, so it can’t run.
How to fix the /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory error