On Wed, Jan 29, 2014 at 9:23 AM, dE wrote:
> On enabling a unit, by default systemd will put it in a target which has
> been specified in by the unit itself.
>
> Is there any way by which I can make the unit start in any custom target?
> Manual linking or using systemctl?
Just use manual links. C
On enabling a unit, by default systemd will put it in a target which has
been specified in by the unit itself.
Is there any way by which I can make the unit start in any custom
target? Manual linking or using systemctl?
___
systemd-devel mailing list
В Tue, 28 Jan 2014 13:15:38 -0800
David Timothy Strauss пишет:
> Alternatively, we should update the man pages to reflect what the
> DefaultDependencies= option affects.
>
> Zbyszek's argument for the patch, however, is that following the
> recommended WantedBy= behavior already applies the same
Alternatively, we should update the man pages to reflect what the
DefaultDependencies= option affects.
Zbyszek's argument for the patch, however, is that following the
recommended WantedBy= behavior already applies the same Before=
dependency, and anyone doing otherwise ought not to be subjected t
From: David Strauss
---
src/core/path.c | 5 -
src/core/socket.c | 4
src/core/timer.c | 4
3 files changed, 13 deletions(-)
diff --git a/src/core/path.c b/src/core/path.c
index fc7069e..95ed015 100644
--- a/src/core/path.c
+++ b/src/core/path.c
@@ -336,11 +336,6 @@ static int
On Tue, 28.01.14 17:36, Barry Scott (barry.sc...@onelan.co.uk) wrote:
>
> On Tue 28 Jan 2014 08:23:35 David Timothy Strauss wrote:
> > You're using both onelan-player.slice and onelan-players.slice in your
> > example. Correct this first.
>
> Doh! Fixing that mistake makes the cgroup appear.
>
On Tue 28 Jan 2014 08:23:35 David Timothy Strauss wrote:
> You're using both onelan-player.slice and onelan-players.slice in your
> example. Correct this first.
Doh! Fixing that mistake makes the cgroup appear.
Thanks for taking the time to look at this.
systemd does not report an issue with the
thanks to both Amit and Colin. I'm going to see what we can throw
together. Will try to remember to share back what we come up with.
On Mon, Jan 27, 2014 at 6:46 PM, Amit Saha wrote:
>
>
> - Original Message -
> > From: "Greg Swift"
> > To: systemd-devel@lists.freedesktop.org
> > Sen
You're using both onelan-player.slice and onelan-players.slice in your
example. Correct this first.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Tue, 28.01.14 11:43, Richard Maw (richard@codethink.co.uk) wrote:
> On Tue, Jan 28, 2014 at 12:27:14PM +0100, Lennart Poettering wrote:
> > On Mon, 27.01.14 20:17, Zbigniew Jędrzejewski-Szmek
> > (zbys...@kemper.freedesktop.org) wrote:
> > > +int mkostemp_safe(char *pattern, int flags) {
>
On Tue, 28.01.14 12:46, Michał Piotrowski (mkkp...@gmail.com) wrote:
> Hi,
>
> The latest version of systemd - v208 was released 118 days ago. There is
> tremendous amount of changes between v208 and master.
>
> Is there any roadmap for a new release? What's the current systemd release
> process
'Twas brillig, and Michał Piotrowski at 28/01/14 11:46 did gyre and gimble:
> Hi,
>
> The latest version of systemd - v208 was released 118 days ago. There is
> tremendous amount of changes between v208 and master.
>
> Is there any roadmap for a new release? What's the current systemd
> release p
On Tue, Jan 28, 2014 at 12:27:14PM +0100, Lennart Poettering wrote:
> On Mon, 27.01.14 20:17, Zbigniew Jędrzejewski-Szmek
> (zbys...@kemper.freedesktop.org) wrote:
> > +int mkostemp_safe(char *pattern, int flags) {
> > +char *s = pattern + strlen(pattern) - 6;
>
> I don't really like mixi
Hi,
The latest version of systemd - v208 was released 118 days ago. There is
tremendous amount of changes between v208 and master.
Is there any roadmap for a new release? What's the current systemd release
process?
--
Best regards,
Michal
http://eventhorizon.pl/
___
On Tue, Jan 28, 2014 at 12:27 PM, Lennart Poettering
wrote:
> On Mon, 27.01.14 20:17, Zbigniew Jędrzejewski-Szmek
> (zbys...@kemper.freedesktop.org) wrote:
>> +uint64_t tries = TMP_MAX;
>> +int randfd, fd, i;
>> +
>> +assert(streq(s, "XX"));
>> +
>> +randfd =
On Mon, 27.01.14 20:17, Zbigniew Jędrzejewski-Szmek
(zbys...@kemper.freedesktop.org) wrote:
> +for (int i = 0; i < j; i++) {
> +size_t written = 0;
> +
> +while (written < w[i].iov_len) {
> +ssize_t r;
> +
> +
On Mon, Jan 27, 2014 at 7:47 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sat, Jan 25, 2014 at 06:16:38PM +0100, Reindl Harald wrote:
>>
>>
>> Am 25.01.2014 18:09, schrieb Marcos Mello:
>> > Koen Kooi dominion.thruhere.net> writes:
>> > [snip]
>> >>
>> >> To make matters worse, the cylon eye isn't
On Sun, Jan 26, 2014 at 6:21 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> +static int writev_safe(int fd, const struct iovec *w, int j, bool
> async_signal_safe) {
> +if (!async_signal_safe)
> +return writev(fd, w, j);
> +
> +for (int i = 0; i < j; i++) {
> +
Am 28.01.2014 05:27, schrieb Zbigniew Jędrzejewski-Szmek:
>>> after the timeout is reached it continues
>>> the users problem is the silent waiting *before* the timeout
> Done.
>
> After a job has been running for more than 5s, or a failure occurs,
> cylon eye will be shown. Also status will be pr
19 matches
Mail list logo
