You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the location of the PID file is hardcoded at compile time and can be changed with --with-rundir. Is there a reason this can't be a runtime choice, same as --config or --users?
Sure, I don't see why not. It could be both a global parameter and an option, with the latter having precedence. I am not familiar with the network namespaces use case, but I am guessing you would want runtime control of the subauth file as well?
I don't remember what I meant about network namespaces. I'm not interested in that personally. Just wanted to specify the state & configuration files at runtime and not have it hardcoded to the constant value at compile time.
Right now, the location of the PID file is hardcoded at compile time and can be changed with
--with-rundir
. Is there a reason this can't be a runtime choice, same as--config
or--users
?SYSCONFDIR is also hardcoded in the same way:
ksmbd-tools/include/tools.h
Lines 91 to 94 in 1b87279
I understand there was only meant to be one ksmbd running on a system, but with network namespaces, this would be a nice thing to have.
The text was updated successfully, but these errors were encountered: