PNG  IHDR* pHYs+ IDATx]n#; cdLb Ǚ[at¤_:uP}>!Usă cag޿ ֵNu`ݼTâabO7uL&y^wFٝA"l[|ŲHLN밪4*sG3|Dv}?+y߉{OuOAt4Jj.u]Gz*҉sP'VQKbA1u\`& Af;HWj hsO;ogTu uj7S3/QzUr&wS`M$X_L7r2;aE+ώ%vikDA:dR+%KzƉo>eOth$z%: :{WwaQ:wz%4foɹE[9<]#ERINƻv溂E%P1i01 |Jvҗ&{b?9g=^wζXn/lK::90KwrюO\!ջ3uzuGv^;騢wq<Iatv09:tt~hEG`v;3@MNZD.1]L:{ծI3`L(÷ba")Y.iljCɄae#I"1 `3*Bdz>j<fU40⨬%O$3cGt]j%Fߠ_twJ;ABU8vP3uEԑwQ V:h%))LfraqX-ۿX]v-\9I gl8tzX ]ecm)-cgʒ#Uw=Wlێn(0hPP/ӨtQ“&J35 $=]r1{tLuǮ*i0_;NƝ8;-vݏr8+U-kruȕYr0RnC]*ެ(M:]gE;{]tg(#ZJ9y>utRDRMdr9㪩̞zֹb<ģ&wzJM"iI( .ꮅX)Qw:9,i좜\Ԛi7&N0:asϓc];=ΗOӣ APqz93 y $)A*kVHZwBƺnWNaby>XMN*45~ղM6Nvm;A=jֲ.~1}(9`KJ/V F9[=`~[;sRuk]rєT!)iQO)Y$V ی ۤmzWz5IM Zb )ˆC`6 rRa}qNmUfDsWuˤV{ Pݝ'=Kֳbg,UҘVz2ﴻnjNgBb{? ߮tcsͻQuxVCIY۠:(V뺕 ٥2;t`@Fo{Z9`;]wMzU~%UA蛚dI vGq\r82iu +St`cR.6U/M9IENDB`#! /bin/sh # Copyright (c) The Exim Maintainers 2023 # Copyright (c) University of Cambridge, 1995 - 2007 # See the file NOTICE for conditions of use and distribution. # SPDX-License-Identifier: GPL-2.0-or-later # Except when they appear in comments, the following placeholders in this # source are replaced when it is turned into a runnable script: # # CONFIGURE_FILE_USE_NODE # CONFIGURE_FILE # BIN_DIRECTORY # EXIWHAT_PS_CMD # EXIWHAT_PS_ARG # EXIWHAT_KILL_SIGNAL # EXIWHAT_EGREP_ARG # EXIWHAT_MULTIKILL_CMD # EXIWHAT_MULTIKILL_ARG # RM_COMMAND # This file has been so processed. # Shell script for seeing what the exim processes are doing. It gets rid # of the old process log, then sends SIGUSR1 to all exim processes to get # them to write their state to the log. Then it displays the contents of # the log. # The following lines are generated from Exim's configuration file when # this source is built into a script, but you can subsequently edit them # without rebuilding things, as long are you are careful not to overwrite # the script in the next Exim rebuild/install. However, it's best to # arrange your build-time configuration file to get the correct values. rm=/bin/rm # Some operating systems have a command that finds processes that match # certain conditions (by default usually those running specific commands) # and sends them signals. If such a command is defined for your OS, the # following variables are set and used. multikill_cmd=killall multikill_arg=exim # In other operating systems, Exim has to use "ps" and "grep" to find the # processes itself. In those cases, the next three variables are used: ps_cmd=/bin/ps ps_arg=ax egrep_arg='/exim( |$)' # In both cases, kill_arg is the argument for the (multi)kill command to send # SIGUSR1 (at least one OS requires a numeric value). signal=-USR1 # See if this installation is using the esoteric "USE_NODE" feature of Exim, # in which it uses the host's name as a suffix for the configuration file name. if [ "x$1" = x--version -o "x$1" = x-v ] then echo "`basename $0`: $0" echo "build: 4.99.1" exit 0 fi if [ "" = "yes" ]; then hostsuffix=.`uname -n` fi # Now find the configuration file name. This has got complicated because # CONFIGURE_FILE may now be a list of files. The one that is used is the first # one that exists. Mimic the code in readconf.c by testing first for the # suffixed file in each case. set `awk -F: '{ for (i = 1; i <= NF; i++) print $i }' </dev/null 2>&1; then $multikill_cmd $signal "$multikill_arg" # No multikill command; do it the hard way else $ps_cmd $ps_arg | \ grep -E "$egrep_arg" | \ awk "{print \"kill $signal \"\$1}" | \ uniq | sh fi sleep 1 if [ ! -s ${log} ] ; then echo "No exim process data" ; else sort -nu ${log} ; fi # End of exiwhat