The wrong status is being transmitted

[khromenokroman]

авг 20 20:10:38 eve-deb systemd[1]: Starting test-iceoryx.service - Test iceoryx RouDi daemon...
авг 20 20:10:38 eve-deb systemd[1]: Started test-iceoryx.service - Test iceoryx RouDi daemon.
авг 20 20:10:38 eve-deb audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=test-iceoryx comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
авг 20 20:10:38 eve-deb iox-roudi[48315]: Log level set to: [Warning]
авг 20 20:10:38 eve-deb iox-roudi[48315]: Reserving 1538259816 bytes in the shared memory [iceoryx_mgmt]
авг 20 20:10:47 eve-deb iox-roudi[48315]: [ Reserving shared memory successful ]
авг 20 20:10:47 eve-deb iox-roudi[48315]: Reserving 108800000 bytes in the shared memory [ses]
авг 20 20:10:47 eve-deb iox-roudi[48315]: [ Reserving shared memory successful ]
авг 20 20:10:47 eve-deb iox-roudi[48315]: RouDi is ready for clients

start in 20:10:38
ready in 20:10:47

when I run through systemd, it turns out that roudi started and systemd said that everything was fine, I started based on this, I'm trying to write something, but in fact it's just starting

unit file:

$ cat /usr/lib/systemd/system/test-iceoryx.service 
[Unit]
Description=TEST iceoryx RouDi daemon

PartOf=test.target

[Service]
Type=exec
ExecStart=iox-roudi -c /usr/share/test/iceoryx/test-iceoryx.toml
User=ses
Restart=always
RestartSec=10
TimeoutStartSec=10

[Install]
WantedBy=multi-user.target

configuration file:

$ cat /usr/share/test/iceoryx/test-iceoryx.toml
[general]
version = 1

[[segment]]

[[segment.mempool]]
size = 32
count = 10000

[[segment.mempool]]
size = 128
count = 10000

[[segment.mempool]]
size = 1024
count = 100000

@elBoberido please help me, we can solve this problem

[elBoberido]

I'm not quite sure what you mean. If you want to let systemd start and stop RouDi, then I must disappoint you, RouDi does not support the systemd readiness protocol which would be required in order to make it work with systemd.

[elfenpiff]

@elBoberido would this be something for iceoryx2 to support the systemd readiness protocol?

[khromenokroman]

I'm not quite sure what you mean. If you want to let systemd start and stop RouDi, then I must disappoint you, RouDi does not support the systemd readiness protocol which would be required in order to make it work with systemd.

@elBoberido RouDi does not support the systemd readiness protocol which would be required in order to make it work with systemd. are you planning to add this functionality to the 1st version of iceoryx?

[elBoberido]

@khromenokroman we are quite busy at the moment with other stuff and iceoryx1 is more or less in maintenance mode. I don't think it will be added anytime soon.

@elfenpiff since iceoryx2 does not need a central daemon, it is up to the application to add systemd support. The only thing that iceoryx2 could do is to provide an abstraction to uniformly do this across multiple OSes. But it would still need something the user has to do explicitly.

[khromenokroman]

@elBoberido Thanks for the reply :)