Displaying 2 results from an estimated 2 matches for "signal_do".
Did you mean:
signal_32
2019 Oct 13
0
After upgrading samba 4.5.10 to 4.9.13
...;samba" ] && daemon_list=${DAEMONNAME}
I 'think' this picks up the 'daemon_list' from '/etc/conf.d/samba' and
uses that if it isn't 'samba', problem is that it isn't 'samba' and
there isn't a daemon called 'samba4'
>
> signal_do() {
> ??????? local signal="$1"
> ??????? [ -z "${signal}" ] && return 0
>
> ??????? local result=0 last_result=0 daemon= cmd_exec=
> ??????? for daemon in ${daemon_list} ; do
> ??????????????? eval cmd_exec=\$${daemon}_${signal}
> ??????????????? if...
2019 Oct 13
4
After upgrading samba 4.5.10 to 4.9.13
Good time!
After upgrading samba 4.5.10 to 4.9.13, name resolution in AD hangs.
# /etc/init.d/samba status
?* status: crashed
But the domain itself works, but hangs when resolving user names.
What can be done?
[2019/10/13 12:24:52.896473, 10, pid=17379, effective(0, 0), real(0, 0),
class=ldb] ../lib/ldb-samba/ldb_wrap.c:77(ldb_wrap_debug)
? ldb: Added timed event