Hi,
I stumbled on this:
$ systemctl cat cron-crontab-pi-0 | grep Environment
Environment=A=a a MAILTO=system-c...@mailinator.com B=b b C=c c
$ systemctl show cron-crontab-pi-0 -p Environment
Environment=A=a a MAILTO=system-c...@mailinator.com B=b b C=c c
- the quotes are gone.
Is this done by
Tom Gundersen t...@jklm.no writes:
On Mon, Oct 27, 2014 at 4:53 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Oct 27, 2014 at 4:48 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
On Sat, 25.10.14 01:36, Tom Gundersen (t...@jklm.no) wrote:
On Mon, Oct 20, 2014 at 9:32 PM, Lennart
On Wed, Oct 29, 2014 at 10:37 AM, Jan Synacek jsyna...@redhat.com wrote:
Tom Gundersen t...@jklm.no writes:
On Mon, Oct 27, 2014 at 4:53 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Oct 27, 2014 at 4:48 PM, Lennart Poettering
mzerq...@0pointer.de wrote:
On Sat, 25.10.14 01:36, Tom Gundersen
---
NEWS | 4
man/journalctl.xml | 4 ++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/NEWS b/NEWS
index 82a1948..d8770a0 100644
--- a/NEWS
+++ b/NEWS
@@ -7,6 +7,10 @@ CHANGES WITH 217:
show log timestamps in the UTC timezone. journalctl now also
Lennart Poettering lenn...@poettering.net writes:
On Tue, 28.10.14 13:14, Lennart Poettering (lenn...@poettering.net) wrote:
On Thu, 23.10.14 16:39, Lennart Poettering (lenn...@poettering.net) wrote:
Heya,
Hmm, I think the generator should already treat the option fields the
same way
Several different systemd tools define a nulstr containing a standard
series of configuration file directories, in /etc, /run, /usr/local/lib,
/usr/lib, and (#ifdef HAVE_SPLIT_USR) /lib. Factor that logic out into
a new helper macro, CONF_DIRS_NULSTR.
---
Realized when defining the Nth instance
This makes it possible to drop in logind configuration snippets from a
package or other configuration management mechanism.
Add documentation to the header of /etc/logind.conf pointing the user at
/etc/logind.conf.d/*.conf.
Introduce a new helper, conf_parse_many, to parse configuration files in
On Wed, Oct 29, 2014 at 09:40:19AM +0100, Alexandre Detiste wrote:
Hi,
I stumbled on this:
$ systemctl cat cron-crontab-pi-0 | grep Environment
Environment=A=a a MAILTO=system-c...@mailinator.com B=b b C=c c
$ systemctl show cron-crontab-pi-0 -p Environment
Environment=A=a a
Why then developers use cmdline before?
Maybe cmdline allow determine disk when bootchart working from or in initrd?
2014-10-28 15:37 GMT+03:00 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
On Tue, Oct 28, 2014 at 07:56:32AM +0300, Timofey Titovets wrote:
Good time of day, list.
I try to fix
On Wed, Oct 29, 2014 at 04:16:22PM +0300, Timofey Titovets wrote:
Why then developers use cmdline before?
Maybe cmdline allow determine disk when bootchart working from or in initrd?
bootchart was merged into systemd after being developed in separate and
often does not follow the same
It helps editing units by either creating a drop-in file, like
/etc/systemd/system/my.service.d/override.conf, or by copying the
original unit from /usr/lib/systemd/ to /etc/systemd/ if the --full
option is specified.
It invokes an editor on temporary files related to the unit files and
if the
---
.gitignore | 1 -
README | 1 -
TODO | 7 ---
3 files changed, 9 deletions(-)
diff --git a/.gitignore b/.gitignore
index 0b71f09..14f1691 100644
--- a/.gitignore
+++ b/.gitignore
@@ -101,7 +101,6 @@
/systemd-quotacheck
/systemd-random-seed
/systemd-rc-local-generator
Lennart Poettering lenn...@poettering.net writes:
On Wed, 15.10.14 11:07, Jan Synacek (jsyna...@redhat.com) wrote:
Hello,
in the documentation for systemd.service, under Type= option, it reads:
Behavior of oneshot is similar to simple; however, it is expected that the
process has to
Simon McVittie wrote on 28/10/14 16:54:
On 28/10/14 16:34, Colin Guthrie wrote:
It seems we have different permissions for /etc/{g}shadow than fedora.
We don't package it as ,root,root but rather 0440,root,shadow.
Who is we? Mageia? FYI, Debian uses 0640 root:shadow for the same files.
When running sysusers we would clobber file ownership and permissions
on the files /etc/passwd, /etc/group and /etc/[g]shadow.
This simply preserves the ownership and mode if existing files are
found.
---
src/sysusers/sysusers.c | 93 ++---
1 file
Colin Guthrie wrote on 29/10/14 14:19:
I'll send a patch in a moment that looks as if it would address this
issue (untested but looks safe enough - could be made a bit more
streamlined if needs be but just left it verbose for now)
And here is another that is more verbose... whichever coding
When running sysusers we would clobber file ownership and permissions
on the files /etc/passwd, /etc/group and /etc/[g]shadow.
This simply preserves the ownership and mode if existing files are
found.
---
src/sysusers/sysusers.c | 61 +
1 file
For a very specific definition of inactive.
I'm looking at a way for the iio-sensor-proxy at:
https://github.com/hadess/iio-sensor-proxy
to suspend reading from accelerometers (or maybe to turn them off), when
all the sessions are locked and the screens turned off.
This would usually mean that I
It helps editing units by either creating a drop-in file, like
/etc/systemd/system/my.service.d/override.conf, or by copying the
original unit from /usr/lib/systemd/ to /etc/systemd/ if the --full
option is specified.
It invokes an editor on temporary files related to the unit files and
if the
On 27.10.2014 15:12, Lennart Poettering wrote:
On Fri, 24.10.14 23:13, Lukasz Stelmach (stl...@poczta.fm) wrote:
On 24.10.2014 00:28, Lennart Poettering wrote:
On Thu, 23.10.14 21:24, Łukasz Stelmach (stl...@poczta.fm) wrote:
+int main(int argc, char *argv[]) {
+struct timex tbuf;
On Wed, Oct 29, 2014 at 01:00:42PM -0400, Daniel Hollocher wrote:
Hey folks,
I'm a not expert here, so please forgive the low quality/interest of my
question.
I'm curious what the ideal systemd way is to set various power management
settings in the /sys tree. For me personally, I'm looking
On Wednesday 29 October 2014 at 13:00:42, Daniel Hollocher wrote:
Hey folks,
I'm a not expert here, so please forgive the low quality/interest of my
question.
I'm curious what the ideal systemd way is to set various power management
settings in the /sys tree. For me personally, I'm
FWIW, I tested this now and it seems to have worked fine and properly
preserved both mode and ownership of the files in question.
OK to push this one?
Col
Colin Guthrie wrote on 29/10/14 14:34:
When running sysusers we would clobber file ownership and permissions
on the files /etc/passwd,
Add syscall numbers for 32 bit x86 and arm and Correct
the system call number for x86_64 (it is 318 not 278)
---
src/shared/missing.h | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/shared/missing.h b/src/shared/missing.h
index 00e0287..7fd259a 100644
---
Yeah, it's tricky.
I don't think sysctl is the answer as that doesn't work with /sys
On Wed, Oct 29, 2014 at 1:06 PM, Ivan Shapovalov intelfx...@gmail.com
wrote:
On Wednesday 29 October 2014 at 13:00:42, Daniel Hollocher wrote:
Hey folks,
I'm a not expert here, so please forgive the low
On Mon, Oct 27, 2014 at 11:20:53PM +0100, Lennart Poettering wrote:
On Mon, 27.10.14 20:16, Michael Scherer (m...@zarb.org) wrote:
On Mon, Oct 27, 2014 at 03:38:37PM +0100, Lennart Poettering wrote:
On Sat, 11.10.14 21:57, m...@zarb.org (m...@zarb.org) wrote:
From: Michael Scherer
2014-10-29 16:20 GMT+03:00 Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl:
On Wed, Oct 29, 2014 at 04:16:22PM +0300, Timofey Titovets wrote:
Why then developers use cmdline before?
Maybe cmdline allow determine disk when bootchart working from or in initrd?
bootchart was merged into systemd
Hi,
I configured a CentOS 7 to limit the amount of memory any single
interactive user can use by setting:
systemctl set-property user.slice MemoryLimit=60G
and excepted root to use a less strict limit:
systemctl set-property user-0.slice MemoryLimit=120G
Works so far, but there's a
On Tue, Oct 28, 2014 at 3:46 PM, Andy Lutomirski l...@amacapital.net wrote:
So far, hidraw_id detects U2F tokens and sets:
ID_U2F_TOKEN=1
ID_SECURITY_TOKEN=1
This causes the uaccess rules to apply to U2F devices.
This works for the Plug-up security key, too.
--Andy
---
I've never
On Wed, 29.10.14 14:29, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
Add syscall numbers for 32 bit x86 and arm and Correct
the system call number for x86_64 (it is 318 not 278)
Hmm? I did my testing on x86_64 3.18rc2, 278 is what worked
here... Did you test 318? Where does that number
Le mercredi 22 octobre 2014, 13:07:39 Lennart Poettering a écrit :
So, I thought myself a couple of times about adding a cron generator
upstream, but always came to the conclusion that having to load the
configuration **twice** during boot-up would be suboptimal.
Well, you can order your reload
On Wed, Oct 29, 2014 at 11:55:29PM +0100, Lennart Poettering wrote:
On Wed, 29.10.14 14:29, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
Add syscall numbers for 32 bit x86 and arm and Correct
the system call number for x86_64 (it is 318 not 278)
Hmm? I did my testing on x86_64
I'm running on kernel
uname -a
Linux desk0107 3.17.1-2.g5c4d099-desktop #1 SMP PREEMPT Sat Oct
18 23:36:23 UTC 2014 (5c4d099) x86_64 x86_64 x86_64 GNU/Linux
with
systemctl --version
systemd 210
+PAM +LIBWRAP +AUDIT +SELINUX -IMA
El 29/10/14 a las #4, Lennart Poettering escribió:
On Wed, 29.10.14 14:29, Cristian Rodríguez (crrodrig...@opensuse.org) wrote:
Add syscall numbers for 32 bit x86 and arm and Correct
the system call number for x86_64 (it is 318 not 278)
Hmm? I did my testing on x86_64 3.18rc2, 278 is what
El 30/10/14 a las #4, Cristian Rodríguez escribió:
El 29/10/14 a las #4, Lennart Poettering escribió:
On Wed, 29.10.14 14:29, Cristian Rodríguez (crrodrig...@opensuse.org)
wrote:
Add syscall numbers for 32 bit x86 and arm and Correct
the system call number for x86_64 (it is 318 not 278)
journalctl across the failed shutdown procedure shows the systemd Power-Off
process starting, the journal stopping, then, a --Reboot--
...
Oct 29 21:02:12 desk0107 systemd[1]: Starting Power-Off...
Oct 29 21:02:12 desk0107 systemd-shutdown[1]: Sending SIGTERM to
36 matches
Mail list logo
