Skip to content

agentwrapper doesn't use LG_USERNAME for rsync and its subprocess #1640

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rossizero opened this issue Mar 27, 2025 · 1 comment
Closed

agentwrapper doesn't use LG_USERNAME for rsync and its subprocess #1640

rossizero opened this issue Mar 27, 2025 · 1 comment

Comments

@rossizero
Copy link

Although the remote client successfully utilizes the LG_USERNAME variable to log in to the remote device via SSH, the agent wrapper does not seem to do the same.

Is there something I might be overlooking? Shouldn't the agent wrapper function similarly to the client in this respect?

@Emantor
Copy link
Member

Emantor commented Apr 8, 2025

The remote client only utilizes LG_USERNAME for locking, this username shouldn't be used for SSH. We expect the username for exporter SSH connections to be set in the users ssh configuration file (~/.ssh/config).

@jluebbe jluebbe closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2025
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

No branches or pull requests

3 participants