> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/automation/os-file-system-cleanup.md). # OS File System Cleanup Automation Regular cleanup of operating system (OS) file systems ensures optimal system performance and helps maintain efficient storage utilization. Unused and obsolete files accumulate over time and can potentially impact system responsiveness. By regularly cleaning up OS file systems, organizations can improve overall system stability, enhance data accessibility, and reduce the risk of encountering storage-related issues such as file fragmentation and disk space shortages. IT-Conductor offers seamless automation of OS file system cleanup on Unix/Linux, delivering enhanced performance management capabilities. It can be applied to one or more systems and can be run manually or on a schedule. This feature is highly adaptable to any customer environment and can become an essential component of IT maintenance operations. ### Prerequisites * The system should be registered in IT-Conductor for monitoring.

Figure 1: Linux/Unix System in IT-Conductor Grid

* A [Robot User](/user-guide/account-administration/create-robot-users.md) should be created and associated with the application/DB/OS users with assigned roles/privileges to execute the local action on the system to be stopped/started.

Figure 2: Start/Stop Process Definitions

* The ownership of the process definition should be assigned to the [Robot User](/user-guide/account-administration/create-robot-users.md). * The [Robot User](/user-guide/account-administration/create-robot-users.md) should be able to view the following recovery definitions when navigating to **Management > Automation > Recovery Definitions**. * Linux File System Cleanup

Figure 3: Navigating to Recovery Definitions

{% hint style="info" %} **Note:** If the recovery definitions are not available for use, contact [IT-Conductor Support](https://docs.itconductor.com/reference/support). {% endhint %} ### Automate OS File System Cleanup 1. Select the file system to implement the OS Filesystem Cleanup automation.

Figure 4: Sybase File System in IT-Conductor Service Grid

2. Click **Used %**.

Figure 5: Sybase File System Used Percentage (%)

3. Click the **Threshold Overrides** icon.

Figure 6: Sybase File System Used Percentage Chart

4. Select the targeted override.

Figure 7: Sybase File System Used Percentage Overrides

{% hint style="info" %} **Note:** Select an override with the maintenance mode not enabled. {% endhint %} 5. Configure the threshold and define the desired schedule for running the OS File System Cleanup automation.

Figure 8: Linux File System Used Space Configuration Settings

6. Select the desired recovery action in the **Recovery** dropdown menu.

Figure 9: Selecting Linux File System Cleanup Recovery Action

7. Select a process owner according to the concept of security and authority.

Figure 10: Selecting File System Cleanup Process Owner

8. Configure to send a notification for this event. (Optional)

Figure 11: Configuring Recovery Notification for Sybase OS File System Cleanup Automation

9. Click **Save** to complete the OS File System Cleanup automation.

Figure 12: Saving the Recovery Configurations for OS File System Cleanup Automation

### View Recovery Activities 1. Click the **Recovery Activities Launched** icon.

Figure 13: Navigating to Recovery Activities Launched

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.itconductor.com/user-guide/automation/os-file-system-cleanup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.