}
      }.start();
    }
  }

  private static class FailStartService extends NoOpService {
    @Override
    protected void doStart() {
      notifyFailed(new IllegalStateException("start failure"));
    }
  }

  private static class FailRunService extends NoOpService {
    @Override
    protected void doStart() {
      super.doStart();

Here are some possible ideas:

* An "Init Container" in Kubernetes that runs before your app container
* A bash script that runs the previous steps and then starts your application
    * You would still need a way to start/restart *that* bash script, detect errors, etc.

/// tip

    
    // First listing should hit the server
    long start1 = System.currentTimeMillis();
    SmbFile[] files1 = dir.listFiles();
    long time1 = System.currentTimeMillis() - start1;
    
    // Second listing should use cache (much faster)
    long start2 = System.currentTimeMillis();
    SmbFile[] files2 = dir.listFiles();
    long time2 = System.currentTimeMillis() - start2;
    
    assertEquals(files1.length, files2.length);

```sh
firewall-cmd --zone=public --add-port=9000/tcp --permanent
```

> [!NOTE]
> `permanent` makes sure the rules are persistent across firewall start, restart or reload. Finally reload the firewall for changes to take effect.

```sh
firewall-cmd --reload
```

### iptables

    }

    /**
     * Displays the start crawling form.
     *
     * @return HTML response for the start crawling form
     */
    @Execute
    @Secured({ ROLE })
    public HtmlResponse startCrawlingForm() {
        saveToken();
        return asHtml(path_AdminWizard_AdminWizardStartJsp).useForm(StartCrawlingForm.class);
    }

    /**
     * Starts the crawling process for all configured crawlers.

    // JVM shutdown will not be prevented from exiting after this service has stopped or failed.
    // Technically this listener is added after start() was called so it is a little gross, but it
    // is called within doStart() so we know that the service cannot terminate or fail concurrently
    // with adding this listener so it is impossible to miss an event that we are interested in.
    addListener(

                        // Simulate the atomic byte tracking operation
                        long start = System.nanoTime();
                        mockBytesEncrypted.addAndGet(1024); // Simulate 1KB message
                        long end = System.nanoTime();

                        totalTime.addAndGet(end - start);
                        operations.incrementAndGet();
                    }

import org.codelibs.fess.util.JobProcess;

import jakarta.annotation.PreDestroy;

/**
 * Helper class for managing system processes in Fess.
 * This class provides functionality to start, stop, and manage external processes
 * such as crawler processes, with proper resource cleanup and lifecycle management.
 */
public class ProcessHelper {
    /** Logger instance for this class */

        throw new UnsupportedOperationException();
    }

    /**
     * Starts a scheduled job by ID.
     *
     * @param id the ID of the scheduled job to start
     * @return JSON response indicating success or failure
     */
    // PUT /api/admin/scheduler/{id}/start
    @Execute(urlPattern = "{}/@word")
    public JsonResponse<ApiResult> put$start(final String id) {
        scheduledJobService.getScheduledJob(id).ifPresent(entity -> {

// Erasure backend for admin-handler tests.
func prepareAdminErasureTestBed(ctx context.Context) (*adminErasureTestBed, error) {
	ctx, cancel := context.WithCancel(ctx)

	// reset global variables to start afresh.
	resetTestGlobals()

	// Set globalIsErasure to indicate that the setup uses an erasure
	// code backend.
	globalIsErasure = true

	// Initializing objectLayer for HealFormatHandler.