system:"name=s1|systemd-config=system=... fails

[thk686]

I am getting:

> Run Plugin 'system' (/usr/local/sdm/plugins/system) Phase post-install with arguments: 
  'name=s1|systemd-config=system=biosense-config-files/remove-ssh-success.service'
* Plugin system: Start Phase post-install
> Plugin system: Copy systemd 'system' config file 
  '/etc/sdm/assets/system-s1/systemd-config/system/*' to /etc/systemd/system.conf.d
cp: cannot stat '/etc/sdm/assets/system-s1/systemd-config/system/*': No such file or directory
chown: cannot access '/etc/systemd/system.conf.d/*': No such file or directory
chmod: cannot access '/etc/systemd/system.conf.d/*': No such file or directory
* Plugin system: Complete Phase post-install
> Run Plugin 'system' (/usr/local/sdm/plugins/system) Phase post-install with arguments: 
  'name=s2|systemd-config=system=biosense-config-files/ssh-retry.service'
* Plugin system: Start Phase post-install
> Plugin system: Copy systemd 'system' config file 
  '/etc/sdm/assets/system-s2/systemd-config/system/*' to /etc/systemd/system.conf.d
cp: cannot stat '/etc/sdm/assets/system-s2/systemd-config/system/*': No such file or directory
chown: cannot access '/etc/systemd/system.conf.d/*': No such file or directory
chmod: cannot access '/etc/systemd/system.conf.d/*': No such file or directory
* Plugin system: Complete Phase post-install

Did I get the syntax wrong?

[gitbls]

It's not clear to me what biosense-config-files is.

Replace that string with /path/to/mysystem.conf. sdm will then copy /path/to/mysystem.conf to /etc/systemd/system.conf.d/mysystem.conf

As another exasmple, you can update timesyncd.conf with:

systemd-config=timesyncd=/somedir/systemd/timesyncd.conf

systemd nicely provides the xxxx.conf.d directories that enable you to override settings for login, system, timesync, and user.

[thk686]

Ah. So full paths. Got it.

[gitbls]

Yes, and the file type MUST be ".conf". sdm doesn't check that.

Based on this I'm updating the system plugin doc to reflect that a full path is required. Thx for pointing that out! 👍

[thk686]

Thanks!Other quick question: rsync options are with or without the leading “—“?Sent from my iPhoneOn Jun 22, 2024, at 5:21 PM, Benn @.***> wrote: Yes, and the file type MUST be ".conf". sdm doesn't check that. Based on this I'm updating the system plugin doc to reflect that a full path is required. Thx for pointing that out! 👍

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[gitbls]

Thanks!Other quick question: rsync options are with or without the leading “—“?

If this is for the copydir plugin argument rsyncopts then yes, the leading slash (or slashes, as the case may be) must be specified. the copydir plugin simply takes the string and drops it into the command line instead of using -a, so you need to include your own -a if you need it.

If I misunderstood, please clarify which rsync options?

Thx