El vie, 3 de oct 2014 a las 10:55 , Aleksei Besogonov
escribió:
With all the recent noise about systemd abusing its position with the
way it takes over logging I’ve been thinking about a way to solve
it.
As far as I understand the following holds:
- Systemd takes over /dev/log socket which is
On 04 Oct 2014, at 00:17, Cameron Norman wrote:
> El vie, 3 de oct 2014 a las 10:55 , Aleksei Besogonov
> escribió:
>> With all the recent noise about systemd abusing its position with the way it
>> takes over logging I’ve been thinking about a way to solve it.
>>
>> As far as I understand the
dbuch@dbuch-laptop ~ % systemctl status systemd-hostnamed.service -l
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service;
static)
Active: failed (Result: timeout) since lør 2014-10-04 08:14:52 CEST; 5h
7min ago
Docs: man:system
Hi
On Fri, Oct 3, 2014 at 10:00 PM, Daniel Buch wrote:
> Hi,
>
> With current git and since 430e21c2f7e77d600257ead56419f51 i keep on getting
> timeout on these units
>
I also occasionally get timeouts on bus-activated systemd services
with -git. I haven't been able to reproduce it consistently.
Hi,
Environment="X='Y' Z"
ExecStart=/bin/echo $X ${X}
results in echo[31266]: Y Z 'Y' Z
i.e., $X not only splits at whitespace, as documented, but also strips quotes.
Is this by design, or is it an implementation accident? Should this behaviour
be changed?
Zbyszek
__
On Sat, 2014-10-04 at 21:24 +0200, Zbigniew Jędrzejewski-Szmek wrote:
> Environment="X='Y' Z"
> ExecStart=/bin/echo $X ${X}
>
> results in echo[31266]: Y Z 'Y' Z
>
> i.e., $X not only splits at whitespace, as documented, but also strips quotes.
> Is this by design, or is it an implementation acci
On Sun, Oct 05, 2014 at 02:30:42AM +0300, Uoti Urpala wrote:
> On Sat, 2014-10-04 at 21:24 +0200, Zbigniew Jędrzejewski-Szmek wrote:
> > Environment="X='Y' Z"
> > ExecStart=/bin/echo $X ${X}
> >
> > results in echo[31266]: Y Z 'Y' Z
> >
> > i.e., $X not only splits at whitespace, as documented, b
It would be good if the test units were more basic, not things
including "Crash recovery kernel arming." This makes it seems like the
contents are substantial to the tests, when they're not. Just run
something like ExecStart=/usr/bin/echo to make it clear that the units
are stubs. Then, anything bu
