These are also considered special by sh and bash.
---
src/shared/fileio.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/shared/fileio.c b/src/shared/fileio.c
index 400a416..617afea 100644
--- a/src/shared/fileio.c
+++ b/src/shared/fileio.c
@@ -529,11 +529,11 @@ static
I would like to ask if the syntax specification for files used as
EnvironmentFile's is available somewhere. I have searched but could not
find anything.
Unfortunately, if you search around the Internet, you can find many issues
with these files' syntax: it is like Bash, but not exactly, it is not
В Sun, 14 Apr 2013 15:56:02 +0300
Nikos Platis пишет:
> I would like to ask if the syntax specification for files used as
> EnvironmentFile's is available somewhere.
man systemd.exec
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
h
On Sun, Apr 14, 2013 at 3:56 PM, Nikos Platis wrote:
> I would like to ask if the syntax specification for files used as
> EnvironmentFile's is available somewhere. I have searched but could not find
> anything.
>
> Unfortunately, if you search around the Internet, you can find many issues
> with
The reason I was asking is that I was witnessing some problems with a
service, which I could attribute to problems with (the syntax of?) the
EnvironmentFile used.
Using at least systemd 201 on Arch Linux, the (seemingly valid) file
provided by the package author would not work (some variables defi
On Sun, Apr 14, 2013 at 4:38 PM, Nikos Platis wrote:
> The reason I was asking is that I was witnessing some problems with a
> service, which I could attribute to problems with (the syntax of?) the
> EnvironmentFile used.
The syntax is fine. It's the parser that's buggy.
--
Mantas Mikulėnas
___
On Sun, Apr 14, 2013 at 4:38 PM, Nikos Platis wrote:
> The reason I was asking is that I was witnessing some problems with a
> service, which I could attribute to problems with (the syntax of?) the
> EnvironmentFile used.
>
> Using at least systemd 201 on Arch Linux, the (seemingly valid) file
> p
On 14/04/13 03:36, David Strauss wrote:
I keep writing lengthy emails about how we can use this as an
opportunity to reduce redundancy and improve consistency, but I should
probably ping you on #systemd IRC to hash it out. I can't think of
anything elegant that doesn't involve altering the existi
Am 14.04.2013 06:42, schrieb Kok:
> On Sat, Apr 13, 2013 at 2:24 PM, Reindl Harald wrote:
>>> - extend the collector to run much longer
>>
>> which scre to change in teh config?
>
> You can modify systemd-readahead-done.timer, basically change:
>
> OnActiveSec=10s
>
> to whatever value you lik
Am 14.04.2013 18:13, schrieb Reindl Harald:
> Am 14.04.2013 06:42, schrieb Kok:
>> You can modify systemd-readahead-done.timer, basically change:
>>
>> OnActiveSec=10s
>>
>> to whatever value you like
>
> thanks, i give it a try with 3600 seconds what should cover
> also a long coffee and mostly
On Sun, Apr 14, 2013 at 03:28:31PM +0100, Steven Hiscocks wrote:
> On 14/04/13 03:36, David Strauss wrote:
> >I keep writing lengthy emails about how we can use this as an
> >opportunity to reduce redundancy and improve consistency, but I should
> >probably ping you on #systemd IRC to hash it out.
On Sun, Apr 14, 2013 at 7:13 PM, Reindl Harald wrote:
> is there any way to get informations what is "collected"
/usr/lib/systemd/systemd-readahead analyze
> and where are the informations stored?
/.readahead
> locate seems not to show any related file
updatedb
--
Mantas Mikulėnas
_
Am 14.04.2013 20:08, schrieb Mantas Mikulėnas:
> On Sun, Apr 14, 2013 at 7:13 PM, Reindl Harald wrote:
>> is there any way to get informations what is "collected"
>
> /usr/lib/systemd/systemd-readahead analyze
thanks for that, alias set
[root@rh:~]$ which readahead_analyze
alias readahead_ana
On Sun, Apr 14, 2013 at 9:13 AM, Reindl Harald wrote:
>
> Am 14.04.2013 06:42, schrieb Kok:
>> On Sat, Apr 13, 2013 at 2:24 PM, Reindl Harald
>> wrote:
- extend the collector to run much longer
>>>
>>> which scre to change in teh config?
>>
>> You can modify systemd-readahead-done.timer, ba
On Sun, Apr 14, 2013 at 10:18 AM, Reindl Harald wrote:
>
>
> Am 14.04.2013 18:13, schrieb Reindl Harald:
>> Am 14.04.2013 06:42, schrieb Kok:
>>> You can modify systemd-readahead-done.timer, basically change:
>>>
>>> OnActiveSec=10s
>>>
>>> to whatever value you like
>>
>> thanks, i give it a try
Am 14.04.2013 20:49, schrieb Kok:
>> a reason i would love to define specific applications which should
>> always get preloaded on boot independent what is collected at runtime
>> what about starting the machine remove vis WOL and never login because
>> some data sync and shutdown 2 hours later - w
On Sun, Apr 14, 2013 at 12:05 PM, Reindl Harald wrote:
> Am 14.04.2013 20:49, schrieb Kok:
>>> a reason i would love to define specific applications which should
>>> always get preloaded on boot independent what is collected at runtime
>>> what about starting the machine remove vis WOL and never l
From: Steven Hiscocks
Changes to _Reader make it match closer to C API, by removing `get_next`
and `get_previous`. A `get_all` method added, which returns dictionary
of fields using C API SD_JOURNAL_FOREACH_DATA macro, which can be used
in conjunction with `next`.
_Reader `get`, `next`, `get_{re
Am 14.04.2013 21:18, schrieb Kok:
> On Sun, Apr 14, 2013 at 12:05 PM, Reindl Harald
> wrote:
>> what about a dbus-triggered instance like cups and other services
>> are fired up after login which creates a /.readahead-usersession
>> proceeded at boot the same way as /.readahead
>
> it does more
On 4-13-13 23:24:22 Reindl Harald wrote:
> Am 13.04.2013 23:08, schrieb Kok:
> > A lot of things are possible and would help this:
> >
> > - change your system to auto-logon your account and start the
> > applications for you. This is possible without any coding.
>
> well, that's a no-go
You mig
On Sun, Apr 14, 2013 at 1:01 PM, Reindl Harald wrote:
>
> Am 14.04.2013 21:18, schrieb Kok:
>> On Sun, Apr 14, 2013 at 12:05 PM, Reindl Harald
>> wrote:
>>> what about a dbus-triggered instance like cups and other services
>>> are fired up after login which creates a /.readahead-usersession
>>>
Am 14.04.2013 22:49, schrieb Garry T. Williams:
> On 4-13-13 23:24:22 Reindl Harald wrote:
>> Am 13.04.2013 23:08, schrieb Kok:
>>> A lot of things are possible and would help this:
>>>
>>> - change your system to auto-logon your account and start the
>>> applications for you. This is possible wit
Am 14.04.2013 23:06, schrieb Kok:
> On Sun, Apr 14, 2013 at 1:01 PM, Reindl Harald wrote:
>> oh, now i realized that systemd-readahead covers any file-type
>> surely it would be bad preloading anything including data
>>
>> please have a look at
>> http://koji.fedoraproject.org/koji/buildinfo?bu
get_timeout_ms is added as a convenience function, since
it is abysmally hard to call clock_gettime() in Python
versions lower than 3.3. And even for Python 3.3 users
it saves a few lines.
---
Hello,
I'd apply this directly, but since we're currently discussing changes
pin the API, I thought it'd
---
NEWS | 10 +-
man/sd_journal_get_cursor.xml | 2 +-
man/systemctl.xml | 2 +-
man/systemd-system.conf.xml | 2 +-
man/systemd.unit.xml | 2 +-
src/core/syscall-list.h | 2 +-
src/core/umount.c | 2 +-
src/login/log
Hi
On Sun, Apr 14, 2013 at 7:37 PM, Anatol Pomozov
wrote:
> ---
> NEWS | 10 +-
> man/sd_journal_get_cursor.xml | 2 +-
> man/systemctl.xml | 2 +-
> man/systemd-system.conf.xml | 2 +-
> man/systemd.unit.xml | 2 +-
> src/core/syscall-
Maybe I'm missing something in the Gist patch, but won't
Reader.get('__REALTIME_TIMESTAMP') fail with "field name is not
valid"?
On Sun, Apr 14, 2013 at 10:49 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sun, Apr 14, 2013 at 03:28:31PM +0100, Steven Hiscocks wrote:
>> On 14/04/13 03:36, David Stra
On Sun, Apr 14, 2013 at 7:42 PM, Anatol Pomozov
wrote:
> I am not sure about this change though. "sevice" looks like a spelling
> as later in code this field is called "service". dbus gurus could you
> please check what name should be used here?
I'm not a DBus expert, but the "sevice" argument is
28 matches
Mail list logo
