On Sun, Apr 21, 2013 at 6:49 PM, Li, Min A min.a...@intel.com wrote:
Hi systemd experts,
I have a question about the dependence of user and system session. At system
session, there is a service which need to be started after X(user session).
At first I added “After=xorg.target” at this
---
man/systemd-tmpfiles.xml|2 ++
units/systemd-static-nodes.service.in |1 +
units/systemd-tmpfiles-clean.service.in |2 +-
units/systemd-tmpfiles-clean.timer |2 +-
units/systemd-tmpfiles-setup.service.in |2 +-
5 files changed, 6 insertions(+), 3
On Mon, Apr 22, 2013 at 3:16 PM, Umut Tezduyar u...@tezduyar.com wrote:
---
man/systemd-tmpfiles.xml|2 ++
units/systemd-static-nodes.service.in |1 +
units/systemd-tmpfiles-clean.service.in |2 +-
units/systemd-tmpfiles-clean.timer |2 +-
Hi,
The way I see it is systemd-tmpfiles-setup.service is no different than
systemd-static-nodes.service except later is restricted to /dev and runs
before udev. Due to this similarity I thought man:systemd-tmpfiles is the
best place to mention of systemd-static-nodes.service. If that is not the
On Mon, 22.04.13 01:49, Li, Min A (min.a...@intel.com) wrote:
Hi systemd experts,
I have a question about the dependence of user and system session. At
system session, there is a service which need to be started after
X(user session).
At first I added After=xorg.target at this service,
On Mon, 22.04.13 00:58, Kok, Auke-jan H (auke-jan.h@intel.com) wrote:
On Sun, Apr 21, 2013 at 6:49 PM, Li, Min A min.a...@intel.com wrote:
Hi systemd experts,
I have a question about the dependence of user and system session. At system
session, there is a service which need to
On Mon, Apr 22, 2013 at 5:13 PM, Umut Tezduyar u...@tezduyar.com wrote:
The way I see it is systemd-tmpfiles-setup.service is no different than
systemd-static-nodes.service except later is restricted to /dev and runs
before udev.
Hm, if we want to take that view, then it might make sense to
On Mon, Apr 22, 2013 at 6:27 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Apr 22, 2013 at 5:13 PM, Umut Tezduyar u...@tezduyar.com wrote:
The way I see it is systemd-tmpfiles-setup.service is no different than
systemd-static-nodes.service except later is restricted to /dev and runs
before
On Thu, Apr 18, 2013 at 12:42:38AM +0200, Kay Sievers wrote:
On Thu, Apr 18, 2013 at 12:28 AM, Josh Triplett j...@joshtriplett.org wrote:
On Thu, Apr 18, 2013 at 12:12:38AM +0200, Kay Sievers wrote:
On Wed, Apr 17, 2013 at 11:49 PM, Josh Triplett j...@joshtriplett.org
wrote:
+ -
On Thu, Apr 18, 2013 at 12:26:15AM +0200, Kay Sievers wrote:
On Wed, Apr 17, 2013 at 11:50 PM, Josh Triplett j...@joshtriplett.org wrote:
---
TODO |5 +
1 file changed, 5 insertions(+)
diff --git a/TODO b/TODO
index eb482d0..6cf632a 100644
--- a/TODO
+++ b/TODO
@@
On Mon, Apr 22, 2013 at 6:37 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Apr 22, 2013 at 6:27 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Apr 22, 2013 at 5:13 PM, Umut Tezduyar u...@tezduyar.com wrote:
The way I see it is systemd-tmpfiles-setup.service is no different than
On Mon, Apr 22, 2013 at 03:16:44PM +0200, Umut Tezduyar wrote:
---
man/systemd-tmpfiles.xml|2 ++
units/systemd-static-nodes.service.in |1 +
units/systemd-tmpfiles-clean.service.in |2 +-
units/systemd-tmpfiles-clean.timer |2 +-
Otherwise, we get SYSLOG_IDENTIFIER=python or something
similar, which is completely useless.
---
Thoughts?
Specifically, I'm not sure if is worthwhile to allow overriding
SYSLOG_IDENTIFIER per message. Maybe this ability should be removed.
Zbyszek
src/python-systemd/journal.py | 11
On 22/04/13 21:31, Zbigniew Jędrzejewski-Szmek wrote:
Otherwise, we get SYSLOG_IDENTIFIER=python or something
similar, which is completely useless.
---
Thoughts?
Specifically, I'm not sure if is worthwhile to allow overriding
SYSLOG_IDENTIFIER per message. Maybe this ability should be removed.
On Mon, Apr 22, 2013 at 09:53:55PM +0100, Steven Hiscocks wrote:
+self._SYSLOG_IDENTIFIER = (_sys.argv[0]
+ if SYSLOG_IDENTIFIER is None
+ else SYSLOG_IDENTIFIER)
How about having the value as
On Mon, Apr 22, 2013 at 9:29 PM, Josh Triplett j...@joshtriplett.org wrote:
On Thu, Apr 18, 2013 at 12:26:15AM +0200, Kay Sievers wrote:
On Wed, Apr 17, 2013 at 11:50 PM, Josh Triplett j...@joshtriplett.org
wrote:
---
TODO |5 +
1 file changed, 5 insertions(+)
diff --git
On 22/04/13 22:15, Zbigniew Jędrzejewski-Szmek wrote:
On Mon, Apr 22, 2013 at 09:53:55PM +0100, Steven Hiscocks wrote:
+self._SYSLOG_IDENTIFIER = (_sys.argv[0]
+ if SYSLOG_IDENTIFIER is None
+
On Mon, Apr 22, 2013 at 11:24:56PM +0200, Kay Sievers wrote:
On Mon, Apr 22, 2013 at 9:29 PM, Josh Triplett j...@joshtriplett.org wrote:
On Thu, Apr 18, 2013 at 12:26:15AM +0200, Kay Sievers wrote:
On Wed, Apr 17, 2013 at 11:50 PM, Josh Triplett j...@joshtriplett.org
wrote:
---
TODO
Am 22.04.2013 23:53, schrieb Josh Triplett:
1) Leave only root in /etc/passwd and /etc/group
why?
2) Add passwd.d and group.d directories in /etc and under /usr, which
accept one record per file (with name given by the filename) and
which do not include UIDs or GIDs
to break any
On Mon, Apr 22, 2013 at 11:53 PM, Josh Triplett j...@joshtriplett.org wrote:
1) Leave only root in /etc/passwd and /etc/group.
Not commenting on the overall idea, but if you are going to do
something like this, at least allow the the files not to exist at all,
and in this case a default entry
On Mon, Apr 22, 2013 at 3:26 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 22.04.2013 23:53, schrieb Josh Triplett:
1) Leave only root in /etc/passwd and /etc/group
why?
2) Add passwd.d and group.d directories in /etc and under /usr, which
accept one record per file (with name
xattrs on cgroup fs were added back in v3.6-rc3-3-g03b1cde. But
we support kernels = 2.6.39, and we also support kernels compiled
w/o xattr support, so it's better to fall back to mounting without
xattr support.
---
Hi Colin,
On Mon, Apr 22, 2013 at 02:53:50PM -0700, Josh Triplett wrote:
+* Support passwd.d and group.d; accumulate a persistent name/number
map, to
+ preserve UID/GID assignments without requiring assignment of unique
IDs at
+ adduser time.
Hmm, how is that related to systemd
]] Josh Triplett
Effectively, treat ID numbers as magic rotating implementation details
that nobody should care about, and names as the primary identifier.
There's this pesky thing called file systems which are pretty reliant on
UID and GID numbers.
Also, if this is to be done, just put it
24 matches
Mail list logo
