Repository navigation
Support collection fixes and additions - #1325
Conversation
wkz
left a comment
There was a problem hiding this comment.
What do you think about having cmd_collect() do one initial check for sudo availability - if it is available, we re-exec the support script with sudo?
Then we don't have to think about it in any of the following commands. I.e., everything that follows can assume that the privileges it has is the maximum available.
It's sure easier for future extensions and additions, but I'd rather like to see it possible to run the script as a less privileged user without So I propose this instead: SUDO=""
if [ "$(id -u)" -ne 0 ]; then
if command -v sudo >/dev/null 2>&1 && sudo -n true 2>/dev/null; then
SUDO="sudo"
fi
fi
export SUDO That way our plugins can always rely on |
This comment was marked as outdated.
This comment was marked as outdated.
Actually disable iitod on Styx DCP-SC-28p to work around #670, this prohibits software control of LEDs, leaving the default HW control, which has proven more stable on this platform. Signed-off-by: Joachim Wiberg <[email protected]>
Attempt to fix permissions with sudo before falling back to $HOME, and verify directory is actually writable before proceeding. Signed-off-by: Joachim Wiberg <[email protected]>
Signed-off-by: Joachim Wiberg <[email protected]>
85e2b9f to
5420fb0
Compare
|
AFK we agreed that extracting |
Description
supportscript to handle case where/var/lib/supportexists and is owned byrootsudoinside script in favor of letting the user decideiitod.confoverride for Styx DCP-SC-28pChecklist
Tick relevant boxes, this PR is-a or has-a: