Skip to content
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

Issue: adwatchd doesn't detect file changing when copying and overriding a file via RDP connection. #1117

Open
2 tasks done
ppppn opened this issue Oct 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ppppn
Copy link

ppppn commented Oct 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues and found none that matched mine

Describe the issue

adwatchd doesn't detect file changing when overriding a file by copying via RDP connection.

Steps to reproduce it

  1. Windows Server 2022 Standard with adwatchd(0.14.2~24.04)
  2. Content of the adwatchd.yaml is below
verbose: 0
dirs:
    - \\example.com\sysvol\example.com\Ubuntu
  1. Reproducing steps are:
    1. Check the version id of \example.com\sysvol\example.com\Ubuntu\GPT.ini
    2. Place a script into \example.com\sysvol\example.com\Ubuntu\scripts. e.g. the script path is \\example.com\sysvol\example.com\Ubuntu\scripts\hello_world.sh
    3. Edit the hello_world.sh script on the local machine.
    4. Copy the modified hello_world.sh via RDP directly onto \\example.com\sysvol\example.com\Ubuntu\scripts\hello_world.sh
  2. Excepted Behaviour: adwatchd detect the file changing and increment version in the GPT.ini.
  3. Actual Behaviour: adwatchd doesn't detect the file changing. it doesn't increment version in the GPT.ini, too.

It seems the issue is limited to the case where copying a file via RDP. I tried the modified script to elsewhere than \\example.com\sysvol\example.com\Ubuntu\scripts\, for example C:\Users\Administrators\Desktop\ and copy it into \\example.com\sysvol\example.com\Ubuntu\scripts\. In this case, the version of GPT.ini is updated as expected. This seems a workaround.

Ubuntu users: System information

N/A.

ubuntu-bug adsys --save=/tmp/report.txt isn't applicable because it is a bug with adwatchd.

Non Ubuntu users: System information

Environment

  • adsys version: please run adsysctl version
  • Distribution: (NAME in /etc/os-release)
  • Distribution version: (VERSION_ID on /etc/os-release):

Log files

Please redact/remove sensitive information:

adsys service logs can be acquired by running `adsysctl service cat -v`.
You can increase the amount of information displayed by increasing the verbosity level (-v) to -vv or -vvv.

Application settings

Please redact/remove sensitive information:

Paste the contents of your adsys.yaml file here, if you created one.

Additional information

No response

Double check your logs

  • I have redacted any sensitive information from the logs
@ppppn ppppn added the bug Something isn't working label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant