Skip to content

Conversation

@p1gp1g
Copy link
Contributor

@p1gp1g p1gp1g commented Jun 29, 2025

Some config files are relative links to /usr, like 20-systemd-ssh-proxy.conf (in /etc/ssh/ssh_config.d) linked to ../../../usr/lib/systemd/ssh_config.d/20-systemd-ssh-proxy.conf, probably because LIBEXECDIR

And /etc/ssh/ssh_config is set with a symlink here

It leads to a broken link:

$ file /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
/etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf: broken symbolic link to ../../../usr/lib/systemd/ssh_config.d/20-systemd-ssh-proxy.conf

These relative links are broken in /usr/share/factory/etc unless /usr is linked to /usr/share/factory/usr

Some config files are relative links to /usr, like
20-systemd-ssh-proxy.conf. These relative links are
broken in /usr/share/factory/etc unless /usr is linked
to /usr/share/factory/usr
@yuwata
Copy link
Member

yuwata commented Jul 3, 2025

What's the problem here? Why the existence of broken symlink matters? Does it cause some packaging issue? Please elaborate more.

@p1gp1g
Copy link
Contributor Author

p1gp1g commented Jul 3, 2025

I'm not sure to get your concern. Concretely, with the example from the 1st comment: ssh .host and ssh machine/* don't work, as expected and configured by systemd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants