>> 27 июня 2014 г., в 21:54, Lennart Poettering
>> написал(а):
>>
>> On Fri, 27.06.14 17:45, Ivan Shapovalov (intelfx...@gmail.com) wrote:
>>
>> I want to lock my current session using a command-line tool (or a D-Bus
>> call).
>>
>> The only apparent way to do this is `loginctl lock-session $
fsck.btrfs and fsck.xfs are documented to return immediately, so there is
little sense in running them. Avoids some user confusion and a few lines
in the logs.
https://bugzilla.redhat.com/show_bug.cgi?id=1098799
---
man/systemd-f...@.service.xml | 15 ---
src/fstab-generator/f
%I specifier unescapes instance name, so
unison@path-to-profile.service instance becomes "path/to/profile"
Best regards,
Alexander
2014-06-29 0:31 GMT+08:00 Moviuro :
> On Sunday 29 June 2014 00:21:33 you wrote:
>> You could just use /etc/systemd/system/unison@instance.service.d/
>> directory to
On Sat, Jun 28, 2014 at 06:15:58PM +0200, Moviuro wrote:
> Hi all,
>
> I am at the moment trying to clean up my units to write some simple ones that
> I just have to link without hardcoding anything in them but am stuck at this
> issue: what to do if my unit requires multiple parameters?
Hi,
sys
On Sunday 29 June 2014 00:21:33 you wrote:
> You could just use /etc/systemd/system/unison@instance.service.d/
> directory to provide service environment variables, this seems to be
> much more convenient way to configure service.
I can't do that because different users may have the same profile na
You could just use /etc/systemd/system/unison@instance.service.d/
directory to provide service environment variables, this seems to be
much more convenient way to configure service.
Best regards,
Alexander
2014-06-29 0:15 GMT+08:00 Moviuro :
> Hi all,
>
> I am at the moment trying to clean up my
Hi all,
I am at the moment trying to clean up my units to write some simple ones that
I just have to link without hardcoding anything in them but am stuck at this
issue: what to do if my unit requires multiple parameters?
E.g. Using unison to sync files, the different variables I have to use ar
This is accomplished by having wait_for_container() return a positive error
code when we would like that error code to make its way to the user. This
is at odds with the CODING_STYLE rule that error codes should be returned
as negative values.
---
src/nspawn/nspawn.c | 21 +
1
This is accomplished by having the return value of wait_for_container be
interpreted as a negative version of the exit status code.
---
src/nspawn/nspawn.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c
index 0a8dc0c..0c89
These two patches both do the same thing, in slightly different ways.
They fix a regression intruduced in commit 113cea8 (present in v213
and 214) where the exit status of nspawn does not reflect the exit
status of the containered process.
Happy hacking,
~ Luke Shumaker
__
Hi Rich,
Your analysis is correct. networkd is not updating the lft.
We should change two things: dracut (or whatever is being used on your
machine) should set an infinite lifetime when using NFS root (IMHO),
and networkd should update the lft (and in particular force-set it to
infinite if Critic
11 matches
Mail list logo
