Re: [systemd-devel] Adding a Timer section to .service files

systemctl start foo.service systemctl enable foo.service systemd tools must be modified/adjusted​ too On Fri, Jul 8, 2016 at 8:08 AM, Mantas Mikulėnas wrote: > On Fri, Jul 8, 2016 at 7:52 AM, One Infinite Loop <6po...@gmail.com> > wrote: > >> Instead of having a .service

[systemd-devel] Adding a Timer section to .service files

Instead of having a .service file and a .timer file why not having a [Timer] section inside a .service file? It would be much more manageable as one file. Of course, if there are users who prefer having .timer files, .timer files will continue to exist. I use systemd 229.

Re: [systemd-devel] Unable to get Systemd to work with Phoenix/Elixir Exrm Release

Hi Andrei, That worked, thank you so much! Here is the final of the hello-phoenix.service: [Unit] Description=hello-phoenix service [Service] WorkingDirectory=/home/hello-phoenix/app/bin ExecStart=/home/hello-phoenix/app/bin/hello_phoenix foreground Environment=MIX_ENV=prod PORT=

Re: [systemd-devel] Unable to get Systemd to work with Phoenix/Elixir Exrm Release

Hi Michael, How did you get this /home/hello-phoenix/app/bin/hello_phoenix script anyway? If it is generated by exrm, I'd suggest to try "hello_phoenix foreground" in ExecStart directive — it'd prevent forking and detaching from console (it is unnecessary if being supervised by systemd).

Re: [systemd-devel] Unable to get Systemd to work with Phoenix/Elixir Exrm Release

On Thu, Jul 07, 2016 at 07:29:20AM -0700, Michael Chavez wrote: > Hello, > > I am a newbie trying to get systemd to load my phoenix/elixir app. > > I have tried many variations of my hello-phoenix service file, the version > that I feel is closest to being correct looks like this: > > [Service]

Re: [systemd-devel] Unable to get Systemd to work with Phoenix/Elixir Exrm Release

Thanks for the reply. I added "Type=forking" and still get same results: ● hello-phoenix.service - hello-phoenix service Loaded: loaded (/etc/systemd/system/hello-phoenix.service; enabled) Active: failed (Result: start-limit) since Thu 2016-07-07 10:59:25 EDT; 23s ago Process: 7139

Re: [systemd-devel] Unable to get Systemd to work with Phoenix/Elixir Exrm Release

> Process: 4281 ExecStart=/home/hello-phoenix/app/bin/hello_phoenix start (code=exited, status=0/SUCCESS) If it's a 'daemon', use Type=forking. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org

[systemd-devel] Unable to get Systemd to work with Phoenix/Elixir Exrm Release

Hello, I am a newbie trying to get systemd to load my phoenix/elixir app. I have tried many variations of my hello-phoenix service file, the version that I feel is closest to being correct looks like this: [Unit] Description=hello-phoenix service [Service]

Re: [systemd-devel] Standardizing names for graphical session units

Andrei Borzenkov [2016-07-07 11:39 +0300]: > Do not we already have "session" concept in logind? Is not session > already stopped when user logs out? Yes, but user systemd units don't "see" the system logind scopes, so you can't relate to them. And the user systemd instance continues to run after

Re: [systemd-devel] Standardizing names for graphical session units

On Thu, Jul 7, 2016 at 11:27 AM, Martin Pitt wrote: > Zbigniew Jędrzejewski-Szmek [2016-07-04 22:20 +]: >> I think we should instead enhance target units to provide missing >> functionality. The most important thing would be to have something >> like PartOf, but more

Re: [systemd-devel] Standardizing names for graphical session units

Zbigniew Jędrzejewski-Szmek [2016-07-04 22:20 +]: > I think we should instead enhance target units to provide missing > functionality. The most important thing would be to have something > like PartOf, but more nicely configured. PartOf=graphical-kde.target > would do the trick, but it would

Re: [systemd-devel] Standardizing names for graphical session units

Martin Pitt [2016-07-07 9:29 +0200]: > I'll go ahead and create a PR with the unit and a manpage, using > graphical-session.target for now. Then the name bikeshedding can be > continued there. https://github.com/systemd/systemd/pull/3678 -- Martin Pitt|

Re: [systemd-devel] Standardizing names for graphical session units

Hello Jóhann, Jóhann B. Guðmundsson [2016-07-06 16:22 +]: > It's more about people will be have hard time distinguish between two or > more type units with the same name but serve two different purposes. I was thinking graphical.target would be nicely symmetrical to the system-level one, but