AM57x Linux SDK 3.01.00.06 systemd issue

Qing

Expert 1385 points

HI,

I am on using AM57xx Linux SDK 3.1.6. About the filesystem. the Systemd has replaced the Sys V.

I have known how to add a startup items under systemd mechanism. But I found some confusing issue

in Ti orignal filesystem.

I know "to startup a service , you must add a foo.service file. and systemctrl enable foo".

But about the matrix-gui2.0 , tiipclad-daemon and so on such services. I just found these service file

in :

/run/systemd/generator.late/tiipclad-daemon.service
/run/systemd/generator.late/graphical.target.wants/tiipclad-daemon.service
/run/systemd/generator.late/multi-user.target.wants/tiipclad-daemon.service
/sys/fs/cgroup/devices/system.slice/tiipclad-daemon.service
/sys/fs/cgroup/pids/system.slice/tiipclad-daemon.service
/sys/fs/cgroup/systemd/system.slice/tiipclad-daemon.service

and no .service in other area(eg. /etc/systemd or /lib/systemd/system/). why?

when I cat the first file, an infomation "# Automatically generated by systemd-sysv-generator"

in this file content.

That is , these is generated by systemd-sysv-generator.

What control the systemd to generate these file, and how can I set these configuration?

I have ever seen a world " Once systemd look this service no unit. it will to lookup the init.d/ script to match

the service name . if matched, it will generate the service 's .service file in /run/systemd/generated.late/."

is right ?

Thank you very much!

Best Regards

Qing

over 9 years ago

0 Biser Gatchev-XID over 9 years ago

TI__Guru**** 393215 points

The software team have been notified. They will respond here.

0 Yordan Kamenov over 9 years ago

TI__Mastermind 42515 points

Hi Qing,

you can check those links for some explanation of how systemd uses systemd-sysv-generator
to run the SystemV init scripts:

www.turnkeylinux.org/.../debugging-systemd-sysv-init-compat
unix.stackexchange.com/.../how-does-systemd-use-etc-init-d-scripts

Regards,
Yordan

0 Qing over 9 years ago in reply to Yordan Kamenov

Expert 1385 points

Hi, Yordan:

Thanks for your response, firstly.

In reality, I have seen these link on the net. But I still can't clear about who make matrix-gui2.0 and tiipc startup them in ti arago filesystem ?

I understand these view about systemd to run systemd-sysv-generator . But tested found that, Once I write a script in /etc/init.d/APP.sh , and APP.service is automaticaly generated in /run/systemd/generated.late/.

But the App.service is not excuted by systemd. I think it is certain that there are some configure fille

setting these application's startup. But I can't find any configuration(or .service file).

Can you point out this configuration file for setting the (init.d scripts ) startup.

Thank you very much!

Best Regards

Qing

0 Qing over 9 years ago in reply to Yordan Kamenov

Expert 1385 points

Hello ?

0 Yordan Kamenov over 9 years ago in reply to Qing

TI__Mastermind 42515 points

Hi Qing,

sorry for the delayed reply. I am not very familiar with the way the systemd runs it's services, but my understanding is that
all services created in "/run/systemd/generator.late/" should be loaded. One thing I can suggest is to try to add links to
your "/etc/init.d/APP.sh" in "/etc/rc?.d" directories (you may check how it is done for "/etc/init.d/tiipclad-daemon.sh").
Those links are used for calling the scripts in different run levels in SysV mechanism, and "systemd-sysv-generator"
translates them into "WantedBy=multi-user.target" (or something similar) into the generated .service file.
Also you should be able to run "systemctl status APP.service" (and other systemctl commands) that can give some hints for
the status of the service.

Regards,
Yordan

0 Qing over 9 years ago in reply to Yordan Kamenov

Expert 1385 points

Hi, Yordan:

Thank you very much.

But I have test the link (from etc/app.sh to /etc/rc?.d/ ), and has no affect on systemd to call this service.

it's confused, Okay, let me look the source code of systemd!

Thank you !

Best Regards

Qing

Processors

Processors forum

AM57x Linux SDK 3.01.00.06 systemd issue