On Tue, 26.10.10 22:04, Andrey Borzenkov ([email protected]) wrote:
> -
> "systemd.log_target=console|kmsg|syslog|syslog-org-kmsg|null\n"
> +
> "systemd.log_target=console|kmsg|syslog|syslog-or-kmsg|null\n"
Thanks!
Applied.
Lennart
--
Lennar
On Tue, 26.10.10 11:26, Bill Nottingham ([email protected]) wrote:
>
> Lennart Poettering ([email protected]) said:
> > In a number of ways:
> >
> > - Primarily it is nearly impossible to use /tmp safely to place a
> > communication
> > socket in: on one hand you need to establish a no
Signed-off-by: Andrey Borzenkov
---
src/main.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/main.c b/src/main.c
index 50325e1..7dad015 100644
--- a/src/main.c
+++ b/src/main.c
@@ -333,7 +333,7 @@ static int parse_proc_cmdline_word(const char *word) {
#ifdef HAVE
Lennart Poettering ([email protected]) said:
> In a number of ways:
>
> - Primarily it is nearly impossible to use /tmp safely to place a
> communication
> socket in: on one hand you need to establish a non-random name, so that
> client and server find each other. On the other hand you
On Tue, 26.10.10 10:33, Bill Nottingham ([email protected]) wrote:
>
> Lennart Poettering ([email protected]) said:
> > > I was looking for non-systemd users - while the user-specific dir
> > > is created, there's no actual data that ends up being written there
> > > (at least on my test d
Lennart Poettering ([email protected]) said:
> > I was looking for non-systemd users - while the user-specific dir
> > is created, there's no actual data that ends up being written there
> > (at least on my test desktop). Perhaps none of the apps in that
> > set are using XDG_RUNTIME_DIR?
>
