Emperornero

I am seeing an error regarding log file locations, but the logs have not been moved from their original generated location. Perhaps a permissions issue? 

EDIT: Plotman's issue was that it is unable to do SYSCALLS from WSL 1. Updating to WSL 2 fixes this issue, but it seems an issue with WSL 2 impacts...

So after further investigation I think this may help solve WSL issues for plotman.  ls -l for the PID that plotman is unable to read the log file shows...

> Also, what about that saws it is open by the process? I see that it is a symlink with goofy write/execute permissions which would sensibly mark it as not...

> What does the `l` as the first entry in the permissions list mean if not symlink? > > Did you look at the link I provided re: wsl? Your...

> Yes, I referenced WSL2 and a thing to deal with performance issues in it. The `l` means symlink just as the `->` indicates that as well. But now that...

I'll have to try the WSL thing later after these plots are done. I don't see it making a difference, as my drives were already mounted, but I'll try it...

I've tried both structures. On Thu, May 13, 2021, 5:26 PM James ***@***.***> wrote: > @Emperornero It might be nothing... but > in your plotman.yaml file have you tried log:...

> With the following code changes it works for my wsl1: > > Add to job.py: > > ```python > def list_fds(procId): > '''List process currently open FDs and their...

> With the following code changes it works for my wsl1: > > Add to job.py: > > ```python > def list_fds(procId): > '''List process currently open FDs and their...