KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#developer-tools #codex #typescript #ai-agents #ai-agent #cli #claude-code #open-source #deepseek-harness #dsh-plugin #python #mcp

gressil

★ 77 Open GitHub ↗

Safe daemonization from within Java

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Gressil uses [jnr-ffi](https://github.com/jnr/jnr-ffi) to provide
daemonization and "forking" for Java processes. It uses
<code>posix_spawn</code> to achieve this, rather than
<code>fork</code> and <code>exec</code>. Spawn is used, rather than
the standard C world idiom of <code>fork</code> followed by
<code>exec</code> as <code>fork</code> is very unsafe on the JVM --
there is no such thing as a critical section which cannot get splatted
by GC reshuffling pointers. Here, the child process is started by spawning
a new process complete with command line, *not* by forking the state of the
parent process.

Usage for daemonization looks like:

```java
package org.skife.gressil.examples;

import org.skife.gressil.Daemon;

import java.io.File;
import java.io.IOException;
import java.util.Arrays;
import java.util.Date;

import static org.skife.gressil.Daemon.remoteDebugOnPort;

public class ChattyDaemon
{
    public static void main(String[] args) throws IOException
    {
        new Daemon().withMainArgs(args)
                    .withPidFile(new File("/tmp/chatty.pid"))
                    .withStdout(new File("/tmp/chatty.out"))
                    .withExtraMainArgs("hello", "world,", "how are you?")
                    .withExtraJvmArgs(remoteDebugOnPort(5005))
                    .daemonize();

while (!Thread.currentThread().isInterrupted()) {
            System.out.println(new Date() + " " + Arrays.toString(args));
            try {
                Thread.sleep(1000);
            }
            catch (InterruptedException e) {
                Thread.currentThread().interrupt();
            }
        }
    }
}
```
In the parent process the call to <code>Daemon#daemonize()</code> will
call <code>System.exit()</code>, in the child process it will return
normally.

The child process, in this case, will also wait for a Java debugger to
attach on port 5005. It will attach stdout to <code>/tmp/chatty.out</code>,
and stdin and stderr will default to <code>/dev/null</code> (which stdout would also attach to
by default if it were not specified).

The easiest way to get started is via maven:

```xml
<dependency>
  <groupId>org.skife.gressil</groupId>
  <artifactId>gressil</artifactId>
  <version>0.0.4</version>
</dependency>
```

gressil

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README