GNU bug report logs -
#75762
[shepherd] Confusion about relative file names
Previous Next
Reported by: Dariqq <dariqq <at> posteo.net>
Date: Wed, 22 Jan 2025 15:32:01 UTC
Severity: normal
Done: Ludovic Courtès <ludo <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #16 received at 75762-done <at> debbugs.gnu.org (full text, mbox):
Hi,
Dariqq <dariqq <at> posteo.net> skribis:
>> The situation actually depends on the action you’re running.
>> Starting from 1a8d686b7fa617d9b1df33858957a240b7e11787, shepherd no
>> longer changes directory to the client’s directory. So now it’s up to
>> its action to interpret file names as it wants. We should update the
>> manual accordingly.
>> Did you have a specific action in mind though?
>>
> I was prototyping a user daemon via 'herd load root' before I was
> ready to commit it to my home-environment and was a bit surprised that
> I had to use the full path resp. a path relative to $HOME. This would
> be consistent with the info in section 3.2 but not what I would
> expect.
Right. I pushed a clarification as
882e56ce168c2ddb014cf35e2767d78778e0ba64.
Thanks!
Ludo’.
This bug report was last modified 99 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.