I created a session bus as system service. And iam connecting to that
session bus. My requirement is like this, that's why I'm doing this.@ Simon.
There is no test program for this. App2 should return the data to app1 and
app1 should show Change in UI. this whole thing taking long time. @ Mantas
El 08-11-2018 a las 11:02, deepan muthusamy escribió:
If I start my application as system service, it is consuming huge
memory. This leads to my system getting slow down.
If I start manually, it's not consuming that much memory.
What can be the possible reasons?
Your application has a memor
On Thu, Nov 8, 2018 at 3:27 PM deepan muthusamy
wrote:
> I have two applications. App1 is UI application. App2 is console
> application.
> Both are communicating through Dbus(session). If I press a button in app1,
> aap2 should receive the data immediately.
>
> If I start both of them manually ,
On Thu, 08 Nov 2018 at 18:57:35 +0530, deepan muthusamy wrote:
> I have two applications. App1 is UI application. App2 is console application.
> Both are communicating through Dbus(session).
...
> If I start as system service
System services are not part of any session, so they should not attempt
On Do, 08.11.18 19:32, deepan muthusamy (deepan.m2...@gmail.com) wrote:
> If I start my application as system service, it is consuming huge memory.
> This leads to my system getting slow down.
> If I start manually, it's not consuming that much memory.
Well, that's probably something to ask the d
If I start my application as system service, it is consuming huge memory.
This leads to my system getting slow down.
If I start manually, it's not consuming that much memory.
What can be the possible reasons?
___
systemd-devel mailing list
systemd-devel@
I have two applications. App1 is UI application. App2 is console
application.
Both are communicating through Dbus(session). If I press a button in app1,
aap2 should receive the data immediately.
If I start both of them manually , they are working as expected.
If I start as system service, it is
On Thu, Nov 8, 2018 at 11:33 AM Lennart Poettering
wrote:
>
> On Do, 08.11.18 11:24, Piotr Dobrogost (2...@p.dobrogost.net) wrote:
>
> > Additional question; is there a way to find out which type of hierarchy
> > does systemd use?
>
> Try this:
>
> stat -fc %T /sys/fs/cgroup/
>
> if that reports "
On Thu, Nov 8, 2018 at 9:35 AM Daniel Drake wrote:
>
> Hi,
>
> On Endless we have the following eos-autoupdater.timer:
>
> [Unit]
> Description=Endless OS Automatic Update Timer
> Documentation=man:eos-autoupdater(8)
> ConditionKernelCommandLine=!endless.live_boot
> ConditionKernelComman
On Do, 08.11.18 11:24, Piotr Dobrogost (2...@p.dobrogost.net) wrote:
> Additional question; is there a way to find out which type of hierarchy
> does systemd use?
Try this:
stat -fc %T /sys/fs/cgroup/
if that reports "cgroups2fs" then you are in full cgroupsv2 mode. If
it returns "tmpfs" then y
Additional question; is there a way to find out which type of hierarchy
does systemd use?
Piotr
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Thu, Nov 8, 2018 at 9:27 AM Lennart Poettering
wrote:
>
> Would love to switch Fedora over yesterday. But Docker/Kubernetes and
> the whole container mess doesn't like cgroupsv2 so far, and given how
> important that is for Fedora I fear it'll not be happening anytime
> soon.
>
> Yes, Google's/
On Do, 08.11.18 08:42, Piotr Dobrogost (2...@p.dobrogost.net) wrote:
> On Wed, Nov 7, 2018 at 5:39 PM Lennart Poettering
> wrote:
> > (…)
> > Note that on hybrid all contorllers are mounted as cgroupsv1, hence
> > hybrid is like legacy in this regard.
> >
> > Or in other words, unless you go full
13 matches
Mail list logo