Config is not getting set correctly in rules file or in attach when using filter --add about appscope

[seanvaleo]

Scenario: running the rules --add command on the host, targeting processes on the host and child containers

No config supplied

• rules file correct (matches default)
• attached procs on host correct (matches default)
• attached procs in containers correct (matches default)

Pipe a config file to stdin

• rules file correct (matches piped in config)
• attached procs on host correct (matches piped in config)
• attached procs in containers correct (matches piped in config)

Pass a path to a config file to --userconfig [file]

• rules file correct (matches provided config)
• attached procs on host correct (matches provided config)
• attached procs in containers correct (matches provided config)

Use flags to set things like metricdest, eventdest, etc.

• rules file correct (matches supplied args)
• attached procs on host correct (matches supplied args)
• attached procs in containers correct (matches supplied args)

[seanvaleo]

after performing a scope inspect, the config in the attached processes do not match the rules file.
repro:

top
sudo ./scope rules --add top # attaches to top and installs scope_rules file
scope inspect # see incorrect config (not the default config)
sudo scope rules # see correct config (default config)

we are putting a config in the rules session directory and the contents are correct
we are adding SCOPE_CONF_PATH to env and it is set to the correct path

it's expected that the loader can see the env var, then writes all SCOPE_ env vars to shared memory, then the constructor reads it on attach.

• is the loader cmdAttach seeing this env var?
• is the library constructor seeing this env var?

[seanvaleo]

something strange is happening.
if i run top then sudo ./scope attach top, the config looks correct (default config).
but when i follow the steps in the previous comment (which is essentially doing the same thing; attaching to top), the config is wrong

[seanvaleo]

i noticed that when attach is run, we create a session directory in /tmp, then create a symlink from /root/.scope/history to that.
i noticed that when rules is run, we create a session directory in the /root/.scope/history dir directly.
in both cases, the config in those directories is accurate. but it is not getting read into the process in the rules case.
is this something to do with it?

i can imagine that the top process cannot get permission to read the config file from the root directory.

[seanvaleo]

ok, for the rules command i now create a /tmp directory and then create a symlink from /root/.scope/history to that.
this solved the problem of config not getting respected on attach.
PR: #1569

[seanvaleo]

Scenario: running the rules --add command on in a container, targeting processes on the host and child containers

No config supplied

• rules file correct (matches default)
• attached procs on host correct (matches default)
• attached procs in containers correct (matches default)

Pipe a config file to stdin

• rules file correct (matches piped in config)
• attached procs on host correct (matches piped in config)
• attached procs in containers correct (matches piped in config)

Pass a path to a config file to --userconfig [file]

• rules file correct (matches provided config)
• attached procs on host correct (matches provided config)
• attached procs in containers correct (matches provided config)

Use flags to set things like metricdest, eventdest, etc.

• rules file correct (matches supplied args)
• attached procs on host correct (matches supplied args)
• attached procs in containers correct (matches supplied args)