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

Xine Media Player Review – Powerful but Outdated

Xine is both an open source multimedia playback engine and a video playback application that's been around for a very long time. The number of people using this application has diminished, and there are few maintained third-party apps that are based on this engine. We'll take a closer look at the application to see why this is happening. Read more

Wine Announcement

The Wine development release 1.7.30 is now available. What's new in this release (see below for details): - More support for fonts in DirectWrite. - Improved ATL thunk support. - A few more C runtime functions. - Regedit import/export fixes. - Various bug fixes. Read more

CoreOS offers private Docker container registries for world+dog

Container-loving Linux vendor CoreOS has made its on-premises Docker container registry software available as a standalone product. Previously, CoreOS Enterprise Registry was only available as part of the company's Premium Managed Linux offering, which it describes as "OS as a service." As of Thursday, it is now available for use with any Docker-enabled OS – and these days, what Linux distro hasn't gone gaga for Docker? Even Microsoft is getting into the act. Read more

Manjaro Works To Make Calamares A Distribution-Independent Installer

The Arch-based Manjaro crew has been developing Calamares, an open-source installation framework they hope will basically lead to being a universal Linux distribution installer. The Manjaro camp has been developing Calamares as a distribution installer framework they'll be using for Manjaro 0.9+ and they also hope other Linux distributions will adopt it so it can become somewhat of a universal Linux installer so each distribution camp no longer keeps needing to write their own installer. Read more