> And this is moot anyway since we only inline single-word programs,
> so we could only do this transformation for single-word programs.
> I cannot imagine anything that would be affected if we do /that/,
> since there aren't any programs that are useful when you run them with
> no arguments from
On Wed, Sep 13, 2023 at 12:00:51AM +0200, Alexandre Detiste wrote:
> I think that the risk that some user start by themselves moving around
> some programs
> around the PATH directories and expect nothing to break is quiet moot.
I don't. Users love putting stuff in /usr/local/{,s}bin. And then
0) I d like to hear what our dear user(s) think about this matter
or more generally about systemd-cron before going further.
John:
I see that you use a "cron-monthly-000loaddelay.timer",
and I guess it's purpose from it's name;
and this workflow may need to be tweaked;
the
Control: tag -1 + confirmed upstream
On Tue, Sep 12, 2023 at 10:11:58PM +0200, Alexandre Detiste wrote:
> In v1.x the trailing "> /dev/null" was purposely chopped of the end of the
> line
> because there wasn't an OnSucces= handler anyway and the goal
> was to further parse the bash-one liner.
>
Control: tag -1 +confirmed
Hi,
I confirm your problem.
In v1.x the trailing "> /dev/null" was purposely chopped of the end of the line
because there wasn't an OnSucces= handler anyway and the goal
was to further parse the bash-one liner.
Some of the brittle bash-parsing has already been
Package: systemd-cron
Version: 2.1.2-1
Severity: normal
Dear Maintainer,
I can put a simple command with a redirect to a file or /dev/null, and
systemd-cron continues to email the output of the command. See the
following excerpt from the email, which shows the command I'm running:
6 matches
Mail list logo
