pueue-start

Resume all tasks in the default group

$ pueue start

$ pueue start [task_id]

$ pueue start [task_id] [task_id]

$ pueue start [[-a|--all]] --children

$ pueue start group [group_name]

pueue-start [OPTIONS]

--config FILE
    Specifies an alternative path to the Pueue configuration file. By default, Pueue looks for pueue.yml in standard configuration directories such as ~/.config/pueue/.

--no-fork
    Prevents the Pueue daemon from detaching and running in the background. When this option is used, the daemon runs in the foreground, which is particularly useful for debugging purposes or when running Pueue under a process supervisor like systemd.

--log-level LEVEL
    Sets the verbosity of the daemon's logging output. Common acceptable levels include error, warn, info, debug, and trace.

The pueue-start command initiates the Pueue daemon, which serves as the core backend process for the pueue command-line task queue system. Running continuously in the background, this daemon is solely responsible for managing all queued tasks, enforcing concurrency limits, executing commands, and maintaining their state and output. It acts as the central hub for all pueue client operations, such as adding, showing, or removing tasks from the queue.

Typically, pueue-start is executed once per user session or configured to run automatically upon system startup (e.g., via a systemd user service). Without the daemon running, most pueue client commands will fail, as they rely on active communication with the daemon to perform their functions. By ensuring the daemon is operational, pueue-start enables users to seamlessly queue, manage, and monitor long-running or resource-intensive tasks in an organized and persistent manner.

The exact behavior and availability of the pueue-start command can vary depending on the Pueue version and installation method. In many modern Pueue setups, its functionality is directly provided by the pueue daemon command. Consequently, pueue-start might be a symbolic link, a wrapper script, or not present as a standalone binary. If the Pueue daemon is already running, executing pueue-start again will typically do nothing or report that the daemon is already active, to prevent multiple instances.

For persistent and automatic daemon management, pueue-start (or pueue daemon) is frequently configured to run as a systemd user service. This setup ensures the daemon starts automatically upon user login and automatically restarts if it crashes, providing continuous task management availability without manual intervention.

The overall behavior and settings of the Pueue daemon, including its working directory, log file locations, default command execution parameters, and concurrent task limits, are primarily controlled by a YAML configuration file, typically found at ~/.config/pueue/pueue.yml.

Pueue, created by Lennart Kuehn, was developed to offer a straightforward and robust command-line task queue for personal use, especially for managing long-running processes. The core functionality of starting the daemon, which is central to Pueue's operation, has been present since its early development. While the command name or invocation might have seen minor changes (e.g., evolving from a dedicated pueue-start binary to a subcommand like pueue daemon), its role in providing the persistent backend for task management remains fundamental to the project's design and evolution.

pueue(1), pueue add(1), pueue status(1), pueue stop(1), pueue reset(1)