Language Selection

English French German Italian Portuguese Spanish

Custom scripting gives users a safe-du

Filed under

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

Why the Open Source Stars Must Align

Open source projects like OpenStack, Docker, OPNFV and OpenDaylight are more supported and better funded than ever before. They mark a broader trend of large, active and well-resourced open source projects that are among the leaders in Big Data, cloud computing, operating systems and development practices. Open source has come a long way in 30 years – and its success marks a new era for the overall OSS community. But success does not come without potential pitfalls. One of the greatest obstacles to project success isn’t the proprietary competition – it’s the lack of communication between large open source projects like OpenStack and Docker. Read more

Myth Busting the Open-Source Cloud Part 1

On the contrary, open-source cloud computing products are designed from the outset with security in mind. For example, there are features such as identity management to monitor who has access to content, and data encryption to safeguard information while it’s at rest or in transit. Furthermore, open-source cloud software is peer-reviewed by community participants, leading to continuous improvements in the quality of security features and mechanisms. This community also monitors and rapidly discloses vulnerabilities and issues, and provides security updates to address them. Read more

What does an adult look like in an open source community?

You're no longer "just an adult." You're now trusted and looked to for opinions on how the community should grow. You're a community elder. You embody the history. You keep the history. You work together with other adults and elders to guide and make the community stronger. And to a certain extent, the community once again looks after you, just as it did in the first phase. Read more