On Tue, Mar 25, 2014 at 3:05 PM, Tim Cuthbertson wrote:
> Hi all,
>
> I've got a socket-activated service, called `myapp-main.service` and
> `myapp-main.socket`. These are part of myapp.target:
>
> $ cat myapp.target
> [Install]
> WantedBy=multi-user.target
>
&g
Hi all,
I've got a socket-activated service, called `myapp-main.service` and
`myapp-main.socket`. These are part of myapp.target:
$ cat myapp.target
[Install]
WantedBy=multi-user.target
$ cat myapp-main.service
[Unit]
After=local-fs.target
After=network.target
Requires=myapp-main.socket
[Servic
I recently noticed loud and sustained disk noise, and iotop reported that
jdb2 was going full throttle on /dev/sda1 (my root partition). I ran
`journalctl -f` to see if anything obvious was wrong, and was greeted with
the following messages:
Jan 03 10:23:04 meep systemd[1]: SELinux policy denies a
On Thu, Jul 18, 2013 at 9:47 AM, Lennart Poettering
wrote:
> On Wed, 17.07.13 22:14, Tim Cuthbertson ([email protected]) wrote:
>
> > Hi Folks,
> >
> > I've posted a serverfault question [0], but it got no answers so I
> thought
> > I'd bring it to th
with the examples I encountered.
I'm hoping there's a better way, can anyone point me in the right direction?
[0]:
http://serverfault.com/questions/521504/systemd-stop-all-uninstalled-units
Thanks,
- Tim Cuthbertson.
(apologies if this email arrives on the list twice, I think the fir
countered.
I'm hoping there's a better way, can anyone point me in the right direction?
[0]:
http://serverfault.com/questions/521504/systemd-stop-all-uninstalled-units
Thanks,
- Tim Cuthbertson.
___
systemd-devel mailing list
systemd-devel@li
Hi all,
I've seen systemd described as a system & session manager, I was
wondering how far the session manager aspect could be taken. Is it
possible to have services run on a per-user basis, that don't require
root access to configure or run?
I'd like to use systemd's features to provide services