On Fri, Jul 3, 2015 at 5:00 AM, RayBloodworth wrote:
> From this boot chart, dbus.service starts after systemd-logind.service, but
> dbus.service takes littile time for launching.
This is a bug, fixed in v209.. commit
8f9c6fe5ff1d59001aecbf3fbf9ca0ed7ff28ba7
On Wed, 01.07.15 14:26, Daniel Tihelka ([email protected]) wrote:
> On Wednesday 01 of July 2015 12:00:59 Dimitri John Ledkov wrote:
> > Heya,
>
> Hello,
> thank for the reply.
>
> > On 1 July 2015 at 11:35, Daniel Tihelka wrote:
> > > Hello,
> > > does anyone have an experience with the use o
On Wed, 01.07.15 12:35, Daniel Tihelka ([email protected]) wrote:
> Hello,
> does anyone have an experience with the use of systemd-tmpfiles for the user
> instance of systemd.
This is currently not nicely supported. And I am not sure it
should. Note that much of what tmpfiles supports is only
On Fri, 03.07.15 17:22, Andrei Borzenkov ([email protected]) wrote:
> On Fri, Jul 3, 2015 at 5:03 PM, Frank Steiner
> wrote:
> > Lennart Poettering wrote
> >
> >> Normally the network mounts should be ordered after network.target,
> >> and wicked before that. Since in systemd the shutdown order
On Fri, 03.07.15 16:03, Frank Steiner ([email protected]) wrote:
> Lennart Poettering wrote
>
> > Normally the network mounts should be ordered after network.target,
> > and wicked before that. Since in systemd the shutdown order is always
> > the inverse of the startup order this wou
On Fri, 03.07.15 14:25, Francis Moreau ([email protected]) wrote:
> >> But in the case of cryptsetup with 'tmp' option, the device can have a
> >> disk label initially, since it's reformatted at each boot.
> >
> > hmm, usually "tmp" is combined with a /dev/urandom key, and hence is
> > effec
On Fri, 03.07.15 13:31, Elias Probst ([email protected]) wrote:
> On 07/02/2015 07:22 AM, Johannes Ernst wrote:
> > Mine takes an awful long time — blocking IO on the device in the awful long
> > meantime — and I’m puzzled why. Does it perhaps copy (deep? references
> > only?) the entire drive
On Fri, Jul 3, 2015 at 5:03 PM, Frank Steiner
wrote:
> Lennart Poettering wrote
>
>> Normally the network mounts should be ordered after network.target,
>> and wicked before that. Since in systemd the shutdown order is always
>> the inverse of the startup order this would mean that the mounts are
Lennart Poettering wrote
> Normally the network mounts should be ordered after network.target,
> and wicked before that. Since in systemd the shutdown order is always
> the inverse of the startup order this would mean that the mounts are
> removed first, and wicked only stopped afterwards.
I gues
Looks like I shouldn't have announced success that early.
Even on a fresh raw-backed machines btrfs volume, I'm running into problems.
What I did:
# re-create btrfs volume
machinectl set-limit 6G
# built a mininmal CentOS7.1 image (yum.conf below):
yum -c /tmp/yum.conf groupinstall Base
# yum.c
On 07/03/2015 01:22 PM, Lennart Poettering wrote:
> B1;4002;0cOn Fri, 03.07.15 13:09, Francis Moreau ([email protected])
> wrote:
>
>>> That's not an issue really. Since the device will not have any disk
>>> label initially, and thus nothing will make use of it, until the
>>> mke2fs is finis
Yes indeed, it is under OpenVZ.
I'll redo the installation under KVM, this should work better.
Thank you very much !!
:-)
> Date: Fri, 3 Jul 2015 09:58:44 +0200
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: [systemd-deve
On 07/02/2015 07:22 AM, Johannes Ernst wrote:
> Mine takes an awful long time — blocking IO on the device in the awful long
> meantime — and I’m puzzled why. Does it perhaps copy (deep? references only?)
> the entire drive?
>
I've seen a similar issue here which was caused by a obviously corru
On Mon, 29.06.15 16:03, Tom Gundersen ([email protected]) wrote:
> On Sat, Jun 27, 2015 at 10:02 PM, Kay Sievers wrote:
> > On Fri, May 22, 2015 at 3:42 PM, Bastien Nocera wrote:
> >> It's moved to the iio-sensor-proxy D-Bus service.
> >> ---
> >> .gitignore | 1 -
> >>
On Fri, 03.07.15 16:46, Pradeepa Kumar ([email protected]) wrote:
> When you say 'Check the "state" instead '
> Did you mean ActiveState ?
Yes!
Sorry for the confusion!
Lennart
--
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd
B1;4002;0cOn Fri, 03.07.15 13:09, Francis Moreau ([email protected]) wrote:
> > That's not an issue really. Since the device will not have any disk
> > label initially, and thus nothing will make use of it, until the
> > mke2fs is finished, and an ext2 label applied. When mke2fs then closes
>
When you say 'Check the "state" instead '
Did you mean ActiveState ?
On Jul 3, 2015 3:39 PM, "Lennart Poettering" wrote:
> On Fri, 03.07.15 15:29, Pradeepa Kumar ([email protected]) wrote:
>
> > I am writing lib which will monitor apps and notify/callback higher level
> > if apps went down.
>
On 07/03/2015 12:18 PM, Lennart Poettering wrote:
> On Fri, 03.07.15 11:53, Francis Moreau ([email protected]) wrote:
>
>> On 07/03/2015 11:08 AM, Lennart Poettering wrote:
>>> On Tue, 30.06.15 17:37, Francis Moreau ([email protected]) wrote:
>>>
Hi,
I have a service 'A' w
On Wed, 01.07.15 13:50, Johannes Ernst ([email protected]) wrote:
> Hey Martin,
>
> thanks, but:
>
> >> My container is degraded because systemd-tmpfiles-setup.service
> >> failed. My understanding is that it should not run in the container
> >> anyway. (Right?)
> >
> > It should run in
On Fri, 03.07.15 12:14, Frank Steiner ([email protected]) wrote:
Heya,
> > This really depends on the network management service you are
> > using. networkd won't shut down any network connections when you
> > terminate it for example.
> >
> > Which one are you using?
>
> it's "wick
On Fri, 03.07.15 11:53, Francis Moreau ([email protected]) wrote:
> On 07/03/2015 11:08 AM, Lennart Poettering wrote:
> > On Tue, 30.06.15 17:37, Francis Moreau ([email protected]) wrote:
> >
> >> Hi,
> >>
> >> I have a service 'A' which creates a device 'X' and does some
> >> configuri
Hi,
Lennart Poettering wrote
>> 1. I want to keep the network running. To avoid problems with dependencies
>>I had to keep it enabled although all the stuff is done in the
>> kernel/initrd.
>>Thus, it shuts down during reboot and the diskless client hangs
>>of course.
>
> This reall
On Fri, 03.07.15 15:29, Pradeepa Kumar ([email protected]) wrote:
> I am writing lib which will monitor apps and notify/callback higher level
> if apps went down.
> How can I achieve this?
> I tried doing this using propertieschanged signal and reading
> substate
We reserve the liberty to in
On Fri, 03.07.15 15:12, Pradeepa Kumar ([email protected]) wrote:
> On Fri, Jul 3, 2015 at 2:12 PM, Lennart Poettering
> wrote:
>
> > On Thu, 02.07.15 10:18, Pradeepa Kumar ([email protected]) wrote:
> >
> > > hi
> > > I am new to systemd.
> > > I am using systemd 208, libdbus-1-3_1.4.18-1
I am writing lib which will monitor apps and notify/callback higher level
if apps went down.
How can I achieve this?
I tried doing this using propertieschanged signal and reading substate
property and that msg does not have old value and new value in the msg.
I noticed that when app go down i get
On 07/03/2015 11:08 AM, Lennart Poettering wrote:
> On Tue, 30.06.15 17:37, Francis Moreau ([email protected]) wrote:
>
>> Hi,
>>
>> I have a service 'A' which creates a device 'X' and does some
>> configuring of the device. The device is created in a 'ExecStart='
>> directive whereas its con
please see my response inline
On Fri, Jul 3, 2015 at 2:12 PM, Lennart Poettering
wrote:
> On Thu, 02.07.15 10:18, Pradeepa Kumar ([email protected]) wrote:
>
> > hi
> > I am new to systemd.
> > I am using systemd 208, libdbus-1-3_1.4.18-1ubuntu1.4_i386.deb
> > I am to monitor unit stop/failur
On Tue, 30.06.15 17:37, Francis Moreau ([email protected]) wrote:
> Hi,
>
> I have a service 'A' which creates a device 'X' and does some
> configuring of the device. The device is created in a 'ExecStart='
> directive whereas its configuration happens during 'ExecStartPost='.
>
> But it se
On Thu, 02.07.15 10:18, Pradeepa Kumar ([email protected]) wrote:
> hi
> I am new to systemd.
> I am using systemd 208, libdbus-1-3_1.4.18-1ubuntu1.4_i386.deb
> I am to monitor unit stop/failure in my application .
> So I am subscribing to propertiesChanged signal and paring SubState.
> The pro
On Thu, 02.07.15 12:24, Frank Steiner ([email protected]) wrote:
> Hi,
>
> for our diskless clients I setup the network and the root fs in the
> kernel/initrd and do two additional mounts in the initrd which are
> specific for every client.
>
> I understand the boot concept with its
On Sun, 28.06.15 18:50, Michał Zegan ([email protected]) wrote:
> Hey. I would like to ask about service vs scope units, both can be
> created programmatically, so what is a difference/usage scenario for
> programmatically created service vs scope units if service would have
> type simple
Hi, Lennart
Thanks for your reply!
> This is ancient. Please report only issues with very recent releases
> of systemd upstream, thanks!
Our system with this version is very stable, I'm afraid it would cause some
problems if we release rootfs with the newest systemd. However, I w
On Wed, 01.07.15 22:22, Johannes Ernst ([email protected]) wrote:
> If I run systemd-nspawn with —ephemeral, it creates a new temporary
> btrfs subvolume, the documentation says.
Correct.
> Mine takes an awful long time — blocking IO on the device in the
> awful long meantime — and I’m pu
On Thu, 02.07.15 14:04, François Vocel ([email protected]) wrote:
> Hello,
>
> I installed Kolab on CentOS 7.
> The amavis service will not start.
Is this under Virtuozzo/OpenVZ or something like this? Or with a
normal CentOS 7 install?
Either way, please direct a question like this to t
Hi, Cristian
Thanks for your reply!
I will test with a current release.
> Your system is most likely overwhelmed by I/O
What if I improve the I/O priority of dbus.service or systemd-logind.service
?
> Date: Fri, 3 Jul 2015 03:02:23 -0300
> Subject: Re: [systemd-devel] 3.
On Fri, 03.07.15 05:05, RayBloodworth ([email protected]) wrote:
> Hi, everyone
>
> I'm optimizing booting performance of my system.
>
> systemd version: 208
This is ancient. Please report only issues with very recent releases
of systemd upstream, thanks!
> platform: freesca
36 matches
Mail list logo
