whatuses 0.2.2

A simple CLI tool to find which process is using a file or port
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93

# WhatUses

A simple, cross-platform CLI tool to identify which processes are using a specific file or listening on a network port.

[![Crates.io](https://img.shields.io/crates/v/whatuses.svg)](https://crates.io/crates/whatuses)
[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

## Features


- **File Investigation**: Find which processes have a specific file open.
- **Port Investigation**: Identify processes listening on a specific TCP/UDP port.
- **Cross-Platform**: Supports Windows and Linux.
- **Detailed Output**: Provides PID, process name, and executable path.

## Installation


### From Source (using Cargo)


If you have Rust installed, you can install `whatuses` directly from source:

```bash
cargo install whatuses
```

### Binary Downloads


Check the [Releases](https://github.com/kaskii/whatuses/releases) page for pre-compiled binaries for Windows and Linux.

## Usage


### Check a File


To see which processes are using a specific file:

```bash
whatuses C:\path\to\your\file.txt
```

Or explicitly using the `--file` flag:

```bash
whatuses --file C:\path\to\your\file.txt
```

On Linux:
```bash
whatuses /path/to/your/file.txt
```

### Check a Port


To see which processes are listening on a specific port:

```bash
whatuses 8080
```

Or explicitly using the `--port` flag:

```bash
whatuses --port 3000
```

### Verbose Mode


For more detailed logging:

```bash
whatuses 8080 --verbose
```

When enabled, verbose mode provides additional insights into the tool's operations, including:
- **Path Resolution**: Shows how file paths are being canonicalized.
- **Search Progress**: Displays the number of active sockets or processes being scanned.
- **Detailed Matches**: Shows protocol and address information for matching network sockets.
- **Internal Lookups**: Logs attempts to resolve executable paths using platform-specific APIs or fallbacks (e.g., for `svchost.exe` on Windows).
- **System Activity**: Indicates when the internal process list is being refreshed.

## Platform Support


### Windows

- **Files**: Uses the Windows Restart Manager API to accurately identify processes holding file locks.
- **Ports**: Uses native Windows APIs via `netstat-esr` to map ports to PIDs.

### Linux

- **Files**: Inspects `/proc/[pid]/fd` to find processes with open file descriptors.
- **Ports**: Parses network information to identify listening processes.

> **Note**: On both platforms, some process information may require elevated privileges to access. If the tool does not find any processes when you expect it should, try running it with **sudo** (Linux) or as **Administrator** (Windows).

## License


This project is licensed under the terms specified in the [LICENSE](LICENSE) file.