>>> Andreas Kempe schrieb am 27.02.2020 um 16:30 in
Nachricht
<22004_1582817465_5E57E0B9_22004_221_1_20200227153051.GF26693@hitomi.actianordic
se>:
> On Thu, Feb 27, 2020 at 10:04:37AM +0100, Jérémy ROSEN wrote:
>> Le mer. 26 févr. 2020 à 10:59, Andreas Kempe a
>> écrit :
>>
>> > Hello
Le jeu. 27 févr. 2020 à 16:30, Andreas Kempe a
écrit :
> On Thu, Feb 27, 2020 at 10:04:37AM +0100, Jérémy ROSEN wrote:
>
> It is somewhat comforting knowing that others are seeing similar
> issues. :)
>
>
And not to far... you're a customer of ours :P
(well... actia in Toulouse is...)
> > I
I am using systemd-journal-upload and systemd-journal-remote to sync logs
between two systems.
Do we have any configuration to filter the logs that are sent by
systemd-journal-upload? Mainly I am interested in filtering the logs by
using message-id.
I am using systemd version 243.
Thank you
--
Do we have a configuration option to change the ownership of core dump
files generated by systemd-coredump?
Mainly I would like to set the ownership group of the coredumps to a custom
group.
I am using systemd version 243.
--
With Kind Regards,
P R Dinesh
On Wed, Feb 26, 2020 at 11:59 AM Andreas Kempe
wrote:
> Hello everyone,
>
> I'm working in a project with an embedded Linux system based on
> Openembedded using Systemd version 241 as our init process. We're
> using a read-only /etc. To facilitate development, we want to use a
> writeable
On Thu, Feb 27, 2020 at 10:04:37AM +0100, Jérémy ROSEN wrote:
> Le mer. 26 févr. 2020 à 10:59, Andreas Kempe a
> écrit :
>
> > Hello everyone,
> >
> > I'm working in a project with an embedded Linux system based on
> > Openembedded using Systemd version 241 as our init process. We're
> > using a
Dear all,
In systend, the order of power off is: first stop all services, and then
uninstall the file system to oldroot. In special applications, if the systemd
need to stop most services first (need to keep some services communicating with
the outside world over the network), then uninstall
I had similar problems with a case of booting with the rootfs read-only and
then becoming read-write later...
Basically systemd only checks for machine-id very early (before reading any
config file) and does not deal well with /etc changing status...
I did a complete analysis of what's going on,
