Re: [systemd-devel] systemd kiosk volatile $HOME
On Wed, Feb 27, 2013 at 10:47 AM, wrote: > Here's the question (systemd version 197). > > https://bbs.archlinux.org/viewtopic.php?pid=1237019 > > Might the answer involve two units, a mount and a service? Thanks much. > I guess it depends on how generic you want it to be. If you need to sync a single filesystem with fixed name, ExecStartPre for a unit that starts logon dialogue looks a right choice. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] pager: add K to less environment
Using less as a pager sometimes breaks terminal when output
is interrupted by ctrl-c.
Reproducer: run 'sudo journalctl' ctrl-c.
Thanks mbr...@redhat.com for the solution.
---
src/shared/pager.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/shared/pager.c b/src/shared/pager.c
index 488a12c..5165d2b 100644
--- a/src/shared/pager.c
+++ b/src/shared/pager.c
@@ -85,7 +85,7 @@ int pager_open(void) {
dup2(fd[0], STDIN_FILENO);
close_pipe(fd);
-setenv("LESS", "FRSX", 0);
+setenv("LESS", "FRSXK", 0);
/* Make sure the pager goes away when the parent dies */
if (prctl(PR_SET_PDEATHSIG, SIGTERM) < 0)
--
1.7.11.7
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd kiosk volatile $HOME
> I guess it depends on how generic you want it to be. If you need to > sync a single filesystem with fixed name, ExecStartPre for a unit that > starts logon dialogue looks a right choice. Andrey I haven't a clue what you said. I hoped some guru might write a unit. I don't imagine one needs more than five or ten lines. What they are, I know not. Generic - I'm unclear of meaning or relevance. We are not syncing a filesystem. We are copying a folder from a persistent filesystem to a tmpfs filesystem. Yet it's a folder that affects user experience and login logistics. It can't be aggressively parallelized without guidance. Our attempts got somehow clobbered by other systemd or OS operations. We need to copy a $HOME folder to tmpfs at boot time, presumably after filesystems are up, and also after default OS user setup, but before tty or graphical logins. It's a oneshot. We use rsync only to bypass 'cp' file globbing holes. Rsync is simpler with dotfiles involved. The $HOME folder lives in fixed locations. The files inside are don't-cares from any systemd unit standpoint. Might anyone write a unit with the correct target(s) and require(s) and options? I thought about two-unit solutions after reading http://mohan43u.wordpress.com/2011/11/07/systemd-for-simple-backup/ Thanks all -- http://www.fastmail.fm - Choose from over 50 domains or use your own ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] On(Resume|suspend|hibernate) in unit files?
Hi: There is buggy, legacy software around which simply does not behave properly when faced with resume/suspend/hibernate which is not always practical to modify or fix. Is there any way to have something like ReloadOnResume=[true|false] StopOnSuspend=[true|false] Or some other mechanism provided by systemd/logind that does not require to use the ugly /usr/lib/systemd/system-sleep/ hooks ? Thanks. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [systemd-commits] 12 commits - src/core src/shared
В Wed, 27 Feb 2013 17:27:16 -0800 (PST) mich...@kemper.freedesktop.org (Michal Schmidt) пишет: > New commits: > commit 03b717a3c4f9348807fc56e7a7d711d72d4ec0cb > Author: Michal Schmidt > Date: Thu Feb 28 00:03:22 2013 +0100 > > core/manager: print status messages about running jobs > > Sometimes the boot gets stuck until a timeout hits. The usual timeouts > are on the order of minutes, so users may lose patience. > > Print animated status messages telling the names of units with running > jobs to make it easy to see what systemd is waiting for. > > The animation looks cooler with a shorter interval, but 1 s is OK and > should not be too hard on slow serial console users. > That's really cool and fixes one of the most frequent complaints about systemd from end-users - lack of information when something goes wrong during boot. How does it integrate with Plymouth? IThat most users will have it and not plain console. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
