Language Selection

English French German Italian Portuguese Spanish

Custom scripting gives users a safe-du

Filed under
HowTos

My company has a Linux cluster with a terabyte of attached storage. Over time we noticed the head node was becoming more overloaded. Inspection of the system showed that users were starting dozens of copies of the du utility to determine disk space usage. This was a natural thing for them to do, because they had a need to know how much disk space was available. A lack of disk space would cause their software builds and tests to fail. The problem was that it takes five to seven hours for a du of the entire shared filesystem. Thus, when the filesystem was nearly full (as it of course usually was), the number of du processes would increase almost exponentially.

To address this problem, we first set up automated nightly disk space reports, so that users could check the status without running du. This still did not solve the problem, as the amount of used space could fluctuate dramatically over the course of 24 hours. Users still wanted and needed to run their own du processes throughout the workday.

While adding more disk space would have solved the problem, we are using a large disk array that is already filled to maximum capacity. In general, users tend to fill up all available disk space anyway, no matter how much you give them.

We then developed a policy: users could run du on any directory they owned. In addition, user du processes would be allowed to run for a maximum of one hour of wall time. Users in the wheel group would be exempt from these restrictions.

I was given the task of developing a tool to implement this policy. Some sort of wrapper around the existing du seemed like an obvious choice: the script could validate the input, abort if an invalid path was given, and terminate the du process if it ran too long.

I wrote a basic bash script in perhaps an hour's time. Then I thought about how to run it, and that is where I ran into trouble. I had thought that I would make the script set user id (setuid) or set group id (setgid) root, i.e. when run by any user it would actually run in the root group. Then, I could change the permissions on the real du so that only root could run it. The result would be that normal users could only access the real du through the wrapper script.

Of course that would make a pretty boring article, and in reality it didn't turn out to be that simple:

Full Story.

More in Tux Machines

Developing Linux Is Essential To Intel's Success

The dominant position of Intel in the server processor market is likely helped by the company's consistent strong support for Linux. Based on the W3Techs chart below, Linux is almost as popular as Windows-based servers are. Read more

Firefox OS heading for Africa — and the U.S. too

Orange announced a $40 “Klif” Firefox OS phone for Africa, and Mozilla says it’s working with Verizon Wireless and others on Firefox OS feature phones. There’s still no evidence that Mozilla’s HTML-focused Firefox OS has made much of a dent in the world smartphone market, where it has been focused on low-end devices sold primarily to emerging markets. Yet, Firefox OS still leads the way among upstart, Linux-based mobile operating systems, and will soon be available in more than 40 markets, this year, on a total of 17 smartphones, according to its latest stats. Meanwhile, the very first Tizen (Samsung Z1) and Ubuntu (BQ Aquaris E4.5) phones have only just shipped, and Jolla’s Sailfish OS based Jolla phones are still mostly limited to Europe. Read more

Why large companies use open source ERP

The main reason larger companies use open source Enterprise Resource Planning (ERP) systems is because they are cheaper and easier to customize. Read more