# io.github.libtmux.SnapshotCapture.SnapshotCapture.processForCreation

- **Module:** io.github.libtmux.SnapshotCapture.SnapshotCapture
- **Package:** io.github.libtmux:libtmux
- **Language:** Java
- **Kind:** method
- **Source:** https://github.com/libtmux/libtmux-java/blob/842228310449e879ebcaa3f910597757c9dbffd6/libtmux/src/main/java/io/github/libtmux/SnapshotCapture.java#L135
- **Page:** https://libtmux.org/en/java/latest/reference/io-github-libtmux-snapshotcapture-snapshotcapture-processforcreation/

```
io.github.libtmux.SnapshotCapture.SnapshotCapture.processForCreation() -> Optional<ServerProcess>
```

As {@link #process}, except a live daemon this client cannot actually talk to is never folded into "no daemon" - used only by {@link Server#versionForCreation}, the one caller for which that distinction matters.

tmux reports both the same way from a client's side: "no server running"/"(No such file or
directory)" for a socket nothing is listening on, and "server exited unexpectedly" for a
daemon that refused this client's handshake - confirmed against the matrix, a 3.2a client
against a 3.7c daemon on the same socket fails the second way, rc 1. {@link #process} still
folds both into "no daemon" for every other caller, which asks "is there a server I can read
from" and for which a daemon this client cannot use is no more usable than none at all.