LINUX / LOCAL CONFIGURATION

systemd service & timer generator

Create a scheduled job or foreground service, with unit files and commands to verify and install them on your own Linux machine. Nothing runs on this site.

Choose the service

Unit name (without suffix)ScopePurposeFile to run (absolute Linux path)Run using

Replace the file path with a real file on your target machine. Direct execution needs an executable file and, for a script, a valid shebang. The selected system account must already exist.

Arguments and working directory (optional)

Literal arguments, one per lineWorking directory (absolute path)

At most 20 argument lines. Shell operators and variable expressions are literal arguments, not a command pipeline. Do not put secrets in arguments; command lines and the journal may be visible on your machine.

Calendar schedule

RepeatMinute (0–59)Hour (0–23)Schedule clockMissed calendar eventMaximum job run time (seconds, 1–86400)

Monthly dates stop at 28 so each month has that date. Target-local schedules use the machine’s clock and DST rules, not this browser’s time zone. Verify the next event with systemd-analyze calendar.

Choose settings and generate the files.

Generated configuration

Review and install on your machine

Download the file(s) into your current directory, review their contents, and run the verification commands first. An existing unit with the same name will be replaced by these install commands; choose a unique name or back it up.

When to use this tool

Use a oneshot service and timer for a scheduled script. Use a foreground service for a program that keeps running without daemonizing. A timer does not create a second instance while its matching service is active. A long-running service uses restart-on-failure, subject to systemd’s start-rate limit.

Installation and diagnosis

The commands verify syntax, install the downloaded files, reload the selected manager, and enable the service or timer. Inspect status and journal output for actual failures. Syntax verification does not prove that paths, interpreter, account and permissions are correct on another machine, or that the application will work.

A user manager may stop at logout. Ask your administrator about lingering if jobs must continue without a login; this generator does not enable it. Journal access and retention depend on the machine. System services need administrator access for installation and use the selected non-root account for execution.

Limits and privacy

This generator supports printable ASCII paths and literal arguments, fixed calendar presets, and modern Linux systemd. Working directories cannot have outer spaces or a final backslash. It does not configure network readiness, mounts, environment secrets, sandbox policies or application dependencies. Inputs stay in this page’s memory; nothing is executed, uploaded, stored or added to a URL.

systemd service reference · systemd timer reference