Re: [systemd-devel] Query regarding "EnvironmentFile"

Am Thu, 10 Dec 2015 01:08:34 +0100 schrieb Reindl Harald : > Am 09.12.2015 um 20:46 schrieb Lennart Poettering: > > I probably should never have added EnvironmentFile= in the first > > place. Packagers misunderstand that unit files are subject to admin > > configuration

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am Mon, 21 Dec 2015 22:41:04 +0100 schrieb Marc Haber : > On Mon, Dec 21, 2015 at 10:18:05PM +0100, Kai Krakow wrote: > > Thus: Please maintainers and developers, remove it. Do not let > > Lennart remove this useful option to force others into removing > > your

[systemd-devel] How to debug machinectl shell?

Hello List, I am running on arch-linux, using systemd 228 and have a machine started using systemd-nspawn. It shows up in machinectl list. I can machinectl login MACHINE into this machine, but when I try to run machinectl shell MACHINE I only get this: Failed to get shell PTY: Cannot set

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Mon, Dec 21, 2015 at 11:14:43PM +0100, Kai Krakow wrote: > I cannot see anything here in the thread which would disallow continue > using non-systemd installations. The problem is that many concepts of systemd are really nice. Once wants to have things like that. The problem is that a minoriy

Re: [systemd-devel] Additional error details when resource limits are exceeded

Am Tue, 22 Dec 2015 08:41:14 +0800 schrieb Peter Hoeg : > Hi, > > >[Service] > >Type=forking > >PIDFile=/run/teamviewerd.pid > >ExecStart=/opt/teamviewer10/tv_bin/teamviewerd -d > >Restart=on-abort > >StartLimitInterval=60 > >StartLimitBurst=10 > > The alternative ExecStart I'm

Re: [systemd-devel] Additional error details when resource limits are exceeded

Am Wed, 9 Dec 2015 11:45:00 +0800 schrieb Peter Hoeg : > Hi, > > it turns out that the teamviewer daemon wasn't behaving correctly and > double-forked before the PID file was written. Fixed by running it as > Type=simple and in the foreground. > > It however, still doesn't

Re: [systemd-devel] systemd (user) and (sd-pam) (user) processes in login shell

Am Tue, 8 Dec 2015 01:36:01 +0200 schrieb Mantas Mikulėnas : > What uid does "oracle" have – is it within the system account range > (usually 1–999) or user account (1000–)? I wonder if it's the latter, > which would mean systemd-logind would clean up various things like > IPC

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Mon, Dec 21, 2015 at 10:18:05PM +0100, Kai Krakow wrote: > Thus: Please maintainers and developers, remove it. Do not let Lennart > remove this useful option to force others into removing your shitty > cruft. This is exactly why systemd is the top one most hated piece of open source software.

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am Mon, 21 Dec 2015 23:29:57 +0100 schrieb Marc Haber : > On Mon, Dec 21, 2015 at 11:14:43PM +0100, Kai Krakow wrote: > > I cannot see anything here in the thread which would disallow > > continue using non-systemd installations. > > The problem is that many

Re: [systemd-devel] Additional error details when resource limits are exceeded

Hi, [Service] Type=forking PIDFile=/run/teamviewerd.pid ExecStart=/opt/teamviewer10/tv_bin/teamviewerd -d Restart=on-abort StartLimitInterval=60 StartLimitBurst=10 The alternative ExecStart I'm using: ExecStart=/opt/teamviewer10/tv_bin/teamviewerd -f And then you can get rid of PIDFile and

Re: [systemd-devel] Is ProtectHome=not working or am I doing something wrong?

2015-12-21 14:16 GMT+01:00 Lennart Poettering : > None of these three settings belong in [Unit]. They belong in [Service]. Yeah, I already figured that out in the mean time, see my earlier reply. Sorry for the confusion. Michael -- Why is it that all of the instruments

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 01:30 PM, Reindl Harald wrote: ExecStart=/path/to/daemon FOO would cut you from distro-changes in other params and explained abvoe sooner or later lead in failing and could even be security relevant depending on new options or removed options in the distro-unit You do

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 21.12.2015 um 15:08 schrieb Jóhann B. Guðmundsson: On 12/21/2015 01:30 PM, Reindl Harald wrote: ExecStart=/path/to/daemon FOO would cut you from distro-changes in other params and explained abvoe sooner or later lead in failing and could even be security relevant depending on new options

Re: [systemd-devel] echo message not coming on terminal with systemd

One more very important observation. On Fri, Dec 18, 2015 at 6:10 AM, Navneet Sinha wrote: > I have systemd service, say xyzWarmup.service. > > Here is the service file > > [Unit] > Description=Xyz agent. > After=fooAfter.service >

Re: [systemd-devel] really strange behaviour after using machinectl shell

I've reported, what I think is the same bug to the gentoo bugtracker. https://bugs.gentoo.org/show_bug.cgi?id=566888 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 21.12.2015 um 14:23 schrieb Jóhann B. Guðmundsson: On 12/21/2015 01:00 PM, Reindl Harald wrote: Am 21.12.2015 um 12:40 schrieb Jóhann B. Guðmundsson: ExecStart=/usr/sbin/foobard $OPTS and then tell admin to use systemctl edit [Unit] Environment=OPTS=-baz bonus points if we could

Re: [systemd-devel] systemd (user) and (sd-pam) (user) processes in login shell

On Mon, Dec 21, 2015 at 7:36 PM, Kai Krakow wrote: > Am Tue, 8 Dec 2015 01:36:01 +0200 > schrieb Mantas Mikulėnas : > >> What uid does "oracle" have – is it within the system account range >> (usually 1–999) or user account (1000–)? I wonder if it's the

Re: [systemd-devel] systemd (user) and (sd-pam) (user) processes in login shell

Am Mon, 21 Dec 2015 21:43:24 -0500 schrieb Mike Gilbert : > On Mon, Dec 21, 2015 at 7:36 PM, Kai Krakow > wrote: > > Am Tue, 8 Dec 2015 01:36:01 +0200 > > schrieb Mantas Mikulėnas : > > > >> What uid does "oracle" have – is it within

Re: [systemd-devel] systemd (user) and (sd-pam) (user) processes in login shell

2015-12-22 3:43 GMT+01:00 Mike Gilbert : > With systemd, you really cannot start daemons from an interactive > shell. Well, there is systemd-run ... -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/18/2015 04:00 PM, Michael Biebl wrote: 2015-12-09 20:46 GMT+01:00 Lennart Poettering : On Wed, 09.12.15 18:27, Soumya Koduri (skod...@redhat.com) wrote: Hi, I have created a systemd.unit(nfs-ganesha.service) file as below : [Unit]

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 21.12.2015 um 12:40 schrieb Jóhann B. Guðmundsson: ExecStart=/usr/sbin/foobard $OPTS and then tell admin to use systemctl edit [Unit] Environment=OPTS=-baz bonus points if we could standardise the $OPTS var name across daemons. Then distros like Fedora could do a one-time migration of

Re: [systemd-devel] Is ProtectHome=not working or am I doing something wrong?

On Sun, 20.12.15 17:33, Michael Biebl (mbi...@gmail.com) wrote: > Hi, > > I'm using systemd v228 and tried to lock down rsyslog a bit. > > For that I added > > # /etc/systemd/system/rsyslog.service.d/override.conf > [Unit] > ProtectSystem=yes > ProtectHome=yes >

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 01:00 PM, Reindl Harald wrote: Am 21.12.2015 um 12:40 schrieb Jóhann B. Guðmundsson: ExecStart=/usr/sbin/foobard $OPTS and then tell admin to use systemctl edit [Unit] Environment=OPTS=-baz bonus points if we could standardise the $OPTS var name across daemons. Then distros

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-21 17:30 GMT+01:00 Jóhann B. Guðmundsson : > It's an added work to add the environmental line to begin with and it's an That would be done once, by upstream ideally. The work would be negligible. > equal amount of work for administrators to change the environmental

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 04:02 PM, Michael Biebl wrote: 2015-12-21 17:00 GMT+01:00 Jóhann B. Guðmundsson : No what's obvious is it does not add any value not et all Well, I can reiterate the points, but I suggest you just read this thread again. and not all daemons and service

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-21 14:23 GMT+01:00 Jóhann B. Guðmundsson : > What he proposed is redundant and adds an extra line to the unit file and in > addition requires some distro's acceptance that upstream needs to be aware > of when it creates the unit for it's daemon/service. > > His proposal

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 02:15 PM, Reindl Harald wrote: and since you say this what is your business for taking "EnvironmentFile" away from administrators area - my config, take your hands from it instead propose to break it - nobody cares if you would something do in a different way as long you are

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 03:17 PM, Michael Biebl wrote: The benefit of that instead of having to override the complete ExecStart line should be obvious and has already be mentioned in this very thread. No what's obvious is it does not add any value not et all and not all daemons and service support

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-21 17:00 GMT+01:00 Jóhann B. Guðmundsson : > No what's obvious is it does not add any value not et all Well, I can reiterate the points, but I suggest you just read this thread again. and not all > daemons and service support additional environmental options added to