]] Lennart Poettering
| I have decided not to merge this part for now. I'd much prefer if ubuntu
| would adopt the lock group too, since everything else appears to be a
| security nightmare to me. Also note that Ubuntu and Debian are in the
| same boat here, so if we merge some fix for this I
Lennart Poettering (lenn...@poettering.net) 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?
Lennart Poettering (lenn...@poettering.net) 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 must
Signed-off-by: Andrey Borzenkov arvidj...@gmail.com
---
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
On Tue, 26.10.10 11:26, Bill Nottingham (nott...@redhat.com) wrote:
Lennart Poettering (lenn...@poettering.net) 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
On Tue, 26.10.10 22:04, Andrey Borzenkov (arvidj...@gmail.com) 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
--
Lennart
