Reading Linux processes with ps
A guide to reading Linux processes: resource use, relationships and states that help with troubleshooting.
In ItalianGNU/Linux administration and troubleshooting
Linux consulting for businesses and IT teams
A slow service, a process using excessive resources or a configuration that is difficult to manage calls for diagnosis and context. Linux consulting helps your team understand the system and plan corrective action.
Understanding and managing Linux systems
For businesses and IT teams that manage GNU/Linux servers in cloud or on-premises environments and need support with administration, reliability or operational issues.
- Unstable services, unusual CPU or memory use, recurring errors and behaviour that is difficult to reproduce.
- Undocumented configurations, fragile manual tasks or incomplete handovers.
- A need to review access, updates, monitoring and administration procedures.
Diagnosis, configuration and procedures
Work starts with the observed problem and available evidence. The distribution, version, application stack and management responsibilities determine the tools and scope of the work.
- Analysis of processes, resources, logs, services and dependencies to develop and test hypotheses.
- Review of the configurations and administration procedures included in the engagement.
- System hardening and automation of repeatable tasks, when relevant to the problem and agreed with the team.
Information and access for a useful diagnosis
Before work begins, we collect distribution and version details, symptoms, event times, recent changes and continuity constraints. Access must be authorised and appropriate to the activities.
- A contact who knows the applications, dependencies and supplier responsibilities.
- Availability of the necessary logs and metrics, handled within the agreed scope.
- Backups, a maintenance window and recovery procedures defined before changes that could affect services.
Support for your actual environment
Compatibility and the work that can be carried out are assessed for your specific environment. Application development, ongoing support, 24/7 coverage and updates to unsupported systems are not automatically included.
- Resolving application problems may require the relevant supplier’s involvement.
- Hardening an individual system is distinct from a security assessment of the entire infrastructure.
- Timelines, coverage and recurring work require specific agreements.
A diagnosis and guidance for your team
Deliverables depend on the engagement: they should explain the problem examined, decisions made and work still needed.
- A summary of observations and checks, including confirmed hypotheses and open questions.
- Documented changes and criteria for checking service behaviour.
- Agreed operating procedures or automation, with guidance on the next steps.
Reading processes and understanding the system
The ps guide explains how to interpret process information; the file security guide explores access and configurations. These public technical articles, written in Italian, help you assess the method and prepare a discussion.
File security on GNU/Linux
Permissions, credentials and configurations: what to check when a standard user account can expose sensitive information or provide access to protected resources.
In ItalianFrequently asked questions
A useful engagement starts with a clear scope from the first discussion.
Which distributions and versions are supported?
The scope depends on the distribution, version and application stack installed in your environment. Include these details and any upgrade constraints in your initial enquiry.
Is ongoing support included?
Project work or troubleshooting does not automatically include ongoing coverage. Coverage, response times and responsibilities for recurring support require a specific agreement.
Describe your Linux environment
Describe your environment, goals and operational constraints. The area of interest is preselected for this service; you can change it in the menu. Marvin is your point of contact. Scope, responsibilities and how the work will be delivered are agreed before the engagement begins.