Re: [systemd-devel] [EXT] Re: Using timedatectl on a readonly rootfile system using mender

2020-09-08 Thread juice

Shravan Singh kirjoitti 2020-09-08 16:31:

No one is answering a simple question. Why we have to guard timezone
so much?.

Why can't I change it? What happens if I change it on a read-only
rootfs? I am breaking the whole systemd by doing this?

In fact most of the people in this group are suggesting a work-around
to me

 "I wonder: If you have a working pull request, why don't you use that
code and be happy with it? That's how free software works.
Still everybody interested can apply you patch."

Yes, it works. My question is why is not getting included so that
everyone can benefit from it. That is how a free software community
should work.


It's a general doubt about usefulness. I don't think your need is so
general that many people would benefit from it and it breaks conventions
that have been used for quite long time.


In this day and age of mobile computing it is really shocking to see.
That timezone is not regarded as something that can be dynamically
changed.


No, that is not the problem here. TZ is freely changeable and always
has been, your problem is the read-only /etc.

You should take this up with mender and not systemd; fix it where it is
broken and don't try to patch it somewhere else.

--
   - Juice -
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] your are happier but without become static some service I can't loggin by console-getty et getty@tty1 services

2020-04-07 Thread juice

Dorian ROSSE kirjoitti 2020-04-08 01:37:

Sorry I was say an error

 I can't start them they happen crash



Normally the getty@ttyX.services are off and are automatically started 
when you start a session on a VT.


Do you get anything relevant on journal?

  - juice -

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] your are happier but without become static some service I can't loggin by console-getty et getty@tty1 services

2020-04-07 Thread juice


Hi Dorian;

I think the main problem is that you use google translate to try to 
express your problems. The translations do not come out as expected, but 
rather broken.


The best thing would be if there was someone native french speaker who 
would be able to help you, then the ideas would not be garbled on 
translation.


  - juice -


Dorian ROSSE kirjoitti 2020-04-07 23:35:

As I was say I am not a systemd worker

 Sorry if you are here just for discuss,

 But please stop to talk to myself for nothing,

 Regards.

 Dorian Rosse.

 Envoyé d’Outlook Mobile [1]
-

From: systemd-devel  on
behalf of Reindl Harald 
Sent: Tuesday, April 7, 2020 10:32:37 PM
To: systemd-devel@lists.freedesktop.org

Subject: Re: [systemd-devel] your are happier but without become
static some service I can't loggin by console-getty et getty@tty1
services

Am 07.04.20 um 22:21 schrieb Dorian ROSSE:

I know there is a coredump mailing list


nothing like a "coredump mailing list" exists
period

you even seem not to know what a coredump ist but crying for it
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Links:
--
[1] https://aka.ms/blhgte
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


--
   - Juice -
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] dockerd broken docker works without It own docker image but need

2020-03-27 Thread Juice
Dorian ROSSE kirjoitti perjantai 27. maaliskuuta 2020:
> I was know a program who finish by "d" is a systemd program instead it real 
> name without the "d"
>

Where do you get these ideas?

  - juice -
 

-- 
Sent from my SFOS/XperiaX
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] Fail to load network modules properly

2019-01-28 Thread juice

Łukasz Słaboń kirjoitti 2019-01-28 11:18:

Apparently the same bug is in the open-source driver. As I said in my
previous e-mail I'm experiencing same problem with all possible
drivers for my wifi card.

Regards,

Łukasz Słaboń



Does your driver require firmware to be loaded before operation?
Is it possible that if the driver starts early enough your /lib/firmware
is not on a mounted partition (or not on initramfs)

  - juice -
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] How to debug occasional hashmap corruption?

2018-11-14 Thread juice

juice kirjoitti 2018-11-06 14:30:

Lennart Poettering kirjoitti 2018-11-06 12:27:

On Di, 06.11.18 11:57, juice (ju...@swagman.org) wrote:



Hi,

During the past half year I have seen systemd dump core three times 
due

to what I suspect a hashmap corruption or race.
Each time it looks a bit different and is triggered by different 
things

but it somehow centers on hashmap operations.

What would be the prefered way to debug this? I cannot add huge 
logging

as this is something that happens once in a blue moon and always in
different compute nodes.
Is there some way I could easily test it by increasing the chance of 
such

corruption/race happening?


This looks very much like a memory corruption of some sorts and
valgrind should be the tool of choice to track that down.

Lennart


Thanks tor the prompt reply, Lennart.

I agree; using valgrind indeed was something already considered, 
however I

suspect it might add some overhead in systemd operation?


I have been trying to start systemd under valgrind but seems it is not a 
trivial
task to do. Moreover, no searching has revealed a general receipe for 
doing that
other than the advice in systemd README's to compile with 
-Dvalgrind=true option.


So, where could I find information on how to set up memory corruption 
debug on

a live system for testing?

 - juice -

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] How to debug occasional hashmap corruption?

2018-11-06 Thread juice

Lennart Poettering kirjoitti 2018-11-06 12:27:

On Di, 06.11.18 11:57, juice (ju...@swagman.org) wrote:



Hi,

During the past half year I have seen systemd dump core three times 
due

to what I suspect a hashmap corruption or race.
Each time it looks a bit different and is triggered by different 
things

but it somehow centers on hashmap operations.

What would be the prefered way to debug this? I cannot add huge 
logging

as this is something that happens once in a blue moon and always in
different compute nodes.
Is there some way I could easily test it by increasing the chance of 
such

corruption/race happening?


This looks very much like a memory corruption of some sorts and
valgrind should be the tool of choice to track that down.

Lennart


Thanks tor the prompt reply, Lennart.

I agree; using valgrind indeed was something already considered, however 
I

suspect it might add some overhead in systemd operation?

The question here was more on the lines how to trigger the problem?
It is quite rare as it seems the occurrance is about once per two months 
on

our QL3 test pool which contains hunderds of VM guests...
It would be impractical to build and deploy a release which contains 
systemd

running under valgrind on every node! :)


--
   - Juice -
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] How to debug occasional hashmap corruption?

2018-11-06 Thread juice
dfa in sd_event_dispatch (e=e@entry=0x5607eb727910) 
at ../src/libsystemd/sd-event/sd-event.c:2667
#15 0x7f13d93f4f89 in sd_event_run (e=0x5607eb727910, 
timeout=1500) at ../src/libsystemd/sd-event/sd-event.c:2727
#16 0x5607e9ad0df4 in manager_loop (m=0x5607eb7273c0) at 
../src/core/manager.c:2615
#17 0x5607e9a8f5a5 in invoke_main_loop 
(ret_error_message=0x7ffe0ed707a8, ret_switch_root_init=pointer>, ret_switch_root_dir=,
ret_fds=0x7ffe0ed707b8, ret_shutdown_verb=, 
ret_retval=, ret_reexecute=, 
m=0x5607eb7273c0) at ../src/core/main.c:1651

#18 main (argc=5, argv=0x7ffe0ed70a98) at ../src/core/main.c:2430
(gdb)


--
   - Juice -
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel