On Tue, Jun 15, 2021 at 1:45 AM Mantas Mikulėnas wrote:
> If you only care about processes on the same system – why not put the
> actual socket in /run, as an AF_UNIX socket? That's mostly what /run is for.
>
I thought of that, but Prometheus cannot scrape AF_UNIX addresses.
Thanks though,
On Mon, Jun 14, 2021 at 9:29 PM Kevin P. Fleming wrote:
> You might consider having systemd itself create the listening sockets
> and then pass them into the service; if you did that, then systemd
> would already know the port number that was allocated for the socket.
>
>
I can't; a .socket unit
A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the
tarball here:
https://github.com/systemd/systemd/archive/v249-rc2.tar.gz
NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production
systems, but please test this and report any issues you find to
On Fr, 25.06.21 11:17, Szymanski, Kai (kai.szyman...@luerssen.de) wrote:
> Hi Lennart,
>
>
> the desciption for StartLimitIntervalSec && Startlimitburst:
>
> "more than burst times within an interval time span are not permitted to
> start any more"
>
>
> But i need: A Job that returns after 4
Hi Lennart,
the desciption for StartLimitIntervalSec && Startlimitburst:
"more than burst times within an interval time span are not permitted to start
any more"
But i need: A Job that returns after 4 Seconds with StatusCode 0 have to be
started again. Of cource i can raise the
On Fr, 25.06.21 09:32, Szymanski, Kai (kai.szyman...@luerssen.de) wrote:
> Hi,
Please always mention the systemd version you are operating with. (And
distro would be good too).
> i have a job that is very fast respawning if there ist nothing todo. The
> Servicefile looks like this:
>
>
>
Hi,
i have a job that is very fast respawning if there ist nothing todo. The
Servicefile looks like this:
[Unit]
Description=job1
StartLimitIntervalSec=100
StartLimitBurst=5
[Service]
Type=idle
User=myuser
Group=mygroup
WorkingDirectory=/tmp
ExecStart=my_fast_respawning_job.sh
Restart=always
