Wrote some scripts to generate systemd .service files and start-up those
services.
Currently just for some REST APIs, but soon will include distributed
systems also.
I set the TCP listen port variable that is used by my .service like so:
`Environment=PORT=4200`
To get PATH to work nicely, my `Ex
I'd like to summarize all the thought about this issue. The systemd
behavior regarding PAM stack has been changed:
1. systemd-232: if PAM stack fails service unit is still started, so PAM
errors are ignored.
2. systemd-233: if PAM stack fails service unit fails as well.
The second is IMO the right
Thanks, that was the information i was looking for.
Indeed i was able to solve the issue!
Again, thank you very much,
Federico
2017-04-30 12:55 GMT+02:00 Lennart Poettering :
> On Sat, 29.04.17 20:31, Federico Di Pierro (nierr...@gmail.com) wrote:
>
> > Hi!
> > I'm struggling to understand if th
On Sun, 30.04.17 00:51, Christian Rebischke (chris.rebisc...@archlinux.org)
wrote:
> Hello everybody,
> I have read in a phoronix article that iwd will be integraded into
> systemd-networkd.[1] Is this already the case with the newest systemd
> version? If not, are there any plans to integrate it
On Sat, 29.04.17 20:31, Federico Di Pierro (nierr...@gmail.com) wrote:
> Hi!
> I'm struggling to understand if this can be done: suppose i start polling
> on sd_bus_get_fd() without any match; then, after some event happens, i add
> a match on same bus.
> Will i receive events on my fd just going
