On Wed, Jun 8, 2016 at 12:48 PM, Florent Peterschmitt
wrote:
> Hi,
>
> I have a recurrent problem at boot time, when mounting filesystems.
>
> First :
>
> o This problem was on systemd v229 and is still here with v230
> o I use BTRFS for everything
> o I have 6 subvolumes
> o I use a subvolume as
8 juin 2016 20:57 "Florent Peterschmitt" a écrit:
> Hi,
>
> I have a recurrent problem at boot time, when mounting filesystems.
>
> First :
>
> o This problem was on systemd v229 and is still here with v230
> o I use BTRFS for everything
> o I have 6 subvolumes
> o I use a subvolume as root fil
Hi,
I have a recurrent problem at boot time, when mounting filesystems.
First :
o This problem was on systemd v229 and is still here with v230
o I use BTRFS for everything
o I have 6 subvolumes
o I use a subvolume as root filesystem, then mount other subvolumes
o I use Gentoo as main distributio
On Wed, 08.06.16 16:58, lejeczek (pelj...@yahoo.co.uk) wrote:
> sorry to bother devel, I've sroogled up but failed to find an answer to this
> simple question - can I get the time that a service takes to start? Also at
> what time after kernel loaded service commenced its startup?
systemctl show
On Wed, Jun 08, 2016 at 06:43:04AM +, Hebenstreit, Michael wrote:
> > Really? No journal messages are getting created at all? No users logging
> > in/out? What does strace show on those processes?
>
> Yes, messages are created - but I'm not interested in them. Maybe a
> user logs in for a
sorry to bother devel, I've sroogled up but failed to find
an answer to this simple question - can I get the time that
a service takes to start? Also at what time after kernel
loaded service commenced its startup?
many thanks,
L.
___
systemd-devel
On 08/06/16 03:04, Hebenstreit, Michael wrote:
>> What processes are showing up in your count? Perhaps it's just a bug that
>> needs to be fixed.
> /bin/dbus-daemon
> /usr/lib/systemd/systemd-journald
> /usr/lib/systemd/systemd-logind
dbus-daemon will wake up when there are D-Bus messages to be
On 06/08/2016 06:51 AM, Hebenstreit, Michael wrote:
Thanks for this and the other suggestions!
So for starters we’ll disable logind and dbus, increase watchdogsec
and see where the footprint is – before disabling journald if
necessary in a next step.
You cannot disable journal but you can
On Tue, 07.06.16 21:00, Greg KH (gre...@linuxfoundation.org) wrote:
> On Wed, Jun 08, 2016 at 02:04:48AM +, Hebenstreit, Michael wrote:
> > > What processes are showing up in your count? Perhaps it's just a
> > > bug that needs to be fixed.
> > /bin/dbus-daemon
> > /usr/lib/systemd/systemd-jo
On Tue, 07.06.16 22:17, Hebenstreit, Michael (michael.hebenstr...@intel.com)
wrote:
> Thanks for the answers
>
> > Well, there's no tracking of sessions anymore, i.e. polkit and all that
> > stuff won't work anymore reasonably, and everything else that involves
> > anything graphical and so o
On Wed, 08.06.16 08:49, Ben-melech, Shiran (shiran.ben-mel...@intel.com) wrote:
> Thank you for the help, I've found that my mistake was initializing the
> sd_event from the main thread while running the loop from the pthread.
> now everything seems to be in order.
>
> Is there a way to cancel th
On Tue, 2016-06-07 at 15:47 +0200, Lennart Poettering wrote:
> On Sun, 05.06.16 13:03, Ben-melech, Shiran (
> shiran.ben-mel...@intel.com) wrote:
>
> > I've added mutex locks over all the sd functions using the bus as
> > well
> > as around the event loop.
> >
> > This is how i run the event loop
12 matches
Mail list logo