Re: [systemd-devel] systemctl enable myunit.service ---> Failed to execute operation: Invalid argument (bobafetthotmail)

On 12/29/2015 09:16 PM, Chaiken, Alison wrote: bobafetthotmail writes: Finally found a workaround, bypassing systemctl. [ . . . ] ln -s /etc/folder2ram/folder2ram.service /lib/systemd/system/local-fs.target.wants/folder2ram.service [ . . . ] On 12/13/2015

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Hi, On Wed, Dec 30, 2015 at 2:52 AM, Michael Chapman wrote: > On Wed, 30 Dec 2015, Reindl Harald wrote: >>> > i am asking for StandardOutput=console get piped to the terminal >>> > systemctl was called - the rest is done by crond as all the years >>> > before >>> >>>

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Reindl Harald [2015-12-30 11:10 +0100]: > i just want systemd *not to touch* the stdout behavior when asked to do so - > it don't need to know anything about ssh ptys, just don't touch stdout > > i am asking for StandardOutput=console get piped to the terminal systemctl > was called - the rest is

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, 30 Dec 2015, Reindl Harald wrote: Standard mailing list etiquette is to reply-to-all on which mailing-list is that the case? be assured it's NOT standard on the majority on most it is considered rude OK. I'm not going to argue the matter. > i am asking for StandardOutput=console

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Reindl Harald [2015-12-30 11:35 +0100]: > in the first mail i wrote: "migrate cronjobs to systemd-units for using > ReadOnlyDirectory and other security otpions" OK, I suggest to use systemd-run -t then, like Michael Chapman already suggested. This should give you both, direct stdout/err and the

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 12:09 schrieb Martin Pitt: Reindl Harald [2015-12-30 11:35 +0100]: in the first mail i wrote: "migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions" OK, I suggest to use systemd-run -t then, like Michael Chapman already suggested. This

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, 30 Dec 2015, Martin Pitt wrote: Reindl Harald [2015-12-30 11:35 +0100]: in the first mail i wrote: "migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions" OK, I suggest to use systemd-run -t then, like Michael Chapman already suggested. This should

[systemd-devel] Do we need /dev/core?

Does anybody know about something actually using /dev/core or is it yet another instance of cargo cult sysadmining? A Debian code search shows only two packages using it. In tests. Wrongly. https://codesearch.debian.net/results/%22%2Fdev%2Fcore%22/page_0 Can we officially deprecate it and then

Re: [systemd-devel] Do we need /dev/core?

On 12/30/2015 11:24 AM, Marco d'Itri wrote: Does anybody know about something actually using /dev/core or is it yet another instance of cargo cult sysadmining? A Debian code search shows only two packages using it. In tests. Wrongly.

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:25 schrieb Michael Chapman: On Wed, 30 Dec 2015, Reindl Harald wrote: Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald > wrote: Do you really have cronjobs

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, 30 Dec 2015, Reindl Harald wrote: Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald > wrote: Do you really have cronjobs which need to output stuff to ssh ptys?

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:52 schrieb Michael Chapman: On Wed, 30 Dec 2015, Reindl Harald wrote: Standard mailing list etiquette is to reply-to-all on which mailing-list is that the case? be assured it's NOT standard on the majority on most it is considered rude OK. I'm not going to argue the

Re: [systemd-devel] Do we need /dev/core?

On Dec 30, "Jóhann B. Guðmundsson" wrote: > You should ask that question on the kernel mailinglist and or on the Debian > devel list if they want to remove that symbolic link to /proc/kcore I am already dealing with the Debian side (and there is no point in removing the link

Re: [systemd-devel] Do we need /dev/core?

On 12/30/2015 11:44 AM, Marco d'Itri wrote: On Dec 30, "Jóhann B. Guðmundsson" wrote: You should ask that question on the kernel mailinglist and or on the Debian devel list if they want to remove that symbolic link to /proc/kcore I am already dealing with the Debian

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, Dec 30, 2015 at 2:40 AM, Reindl Harald wrote: > fine, on a real TTY (CTRL+ALT+F2) the echo appears (cluttered with echo > and the PID instead just the output) but that don't help much in a > SSH-Session.. > > > Am 30.12.2015 um 01:26 schrieb Reindl Harald:

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald wrote: > > > Am 30.12.2015 um 10:37 schrieb Mantas Mikulėnas: > >> On Wed, Dec 30, 2015 at 2:40 AM, Reindl Harald > > wrote: >> >> fine, on a real TTY (CTRL+ALT+F2)

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:24 schrieb Martin Pitt: Reindl Harald [2015-12-30 11:10 +0100]: i just want systemd *not to touch* the stdout behavior when asked to do so - it don't need to know anything about ssh ptys, just don't touch stdout i am asking for StandardOutput=console get piped to the

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 10:37 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 2:40 AM, Reindl Harald > wrote: fine, on a real TTY (CTRL+ALT+F2) the echo appears (cluttered with echo and the PID instead just the output) but that don't

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald > wrote: Do you really have cronjobs which need to output stuff to ssh ptys? i have hundrets cronjobs which are running silent