chkconfig添加服务错误service memcached does not support chkconfig

在Linux系统中，chkconfig是一个用于管理系统服务启动的工具，通过chkconfig，我们可以设置系统在不同运行级别下启动或停止某个服务，在使用chkconfig添加服务时，有时会遇到错误提示“service memcached does not support chkconfig”，这个错误表示memcached服务不支持使用chkconfig进行管理。

我们需要了解为什么会出现这个错误，Memcached是一个高性能的分布式内存对象缓存系统，主要用于减轻数据库负载、提高动态网站访问速度等，它通常以守护进程的方式运行在后台，而不是作为系统服务来管理，当尝试使用chkconfig来管理memcached服务时，系统会返回这个错误。

如何解决这个问题呢？我们可以通过以下几种方法来实现对memcached服务的启动和停止管理：

1、手动启动和停止memcached服务

对于不支持chkconfig管理的memcached服务，我们可以直接通过命令行手动启动和停止服务，以下是一些常用的命令：

启动memcached服务：/usr/local/bin/memcached d m <内存大小> u <用户名> l <监听端口>

停止memcached服务：/usr/local/bin/memcached k flushall

2、编写脚本实现自动启动和停止

为了方便地管理memcached服务，我们可以编写一个脚本来实现自动启动和停止，以下是一个简单的示例：

#!/bin/bash
memcached_control.sh
case "$1" in
    start)
        /usr/local/bin/memcached d m <内存大小> u <用户名> l <监听端口> &
        ;;
    stop)
        /usr/local/bin/memcached k flushall
        ;;
    restart)
        $0 stop
        sleep 1
        $0 start
        ;;
    *)
        echo "Usage: $0 {start|stop|restart}"
        exit 1
esac

将以上脚本保存为memcached_control.sh，并赋予执行权限：chmod +x memcached_control.sh，我们可以通过以下命令来控制memcached服务的启动和停止：

启动memcached服务：./memcached_control.sh start

停止memcached服务：./memcached_control.sh stop

重启memcached服务：./memcached_control.sh restart

3、使用其他工具管理memcached服务

除了手动管理和编写脚本外，我们还可以使用其他工具来管理memcached服务，systemd是Linux系统中的一种初始化系统和服务管理器，它可以用于管理系统服务，虽然memcached本身不支持chkconfig，但我们可以尝试使用systemd来管理它，以下是一个简单的示例：

创建一个名为memcached.service的文件，内容如下：

[Unit]
Description=Memcached Service
After=network.target remotefs.target nsslookup.target
Documentation=man:memcached(1) sysctl:vm.overcommit_memory=1
ConditionPathExists=!/etc/memcached.conf
ConditionPathExists=!/run/memcached.pid
ConditionPathExists=!/var/lib/memcached/*.sock
[Service]
Type=notify
ExecStart=/usr/local/bin/memcached d m <内存大小> u <用户名> l <监听端口> c /etc/memcached.conf P /run/memcached.pid U /var/lib/memcached/*.sock t120 vvv I 60000 D E /var/log/memcached.log f /var/lib/memcached/*.pid syslog background name=%n user=<br />%u maxconnections=%C port=%p socketpath=%S verbosity=%V udpport=%U lockingdirectory=%L pidfile=%F syslogfacility=%F logfile=%E daemonize enablestatistics disabletelnet disablerawresponse prefix=%N %aStartupMessage%n%nUser %u has started the memcached daemon on port %p with options %o%n%aShutdownMessage%n%nUser %u has shut down the memcached daemon on port %p with options %o%n%aRestartMessage%n%nUser %u has restarted the memcached daemon on port %p with options %o%n%aErrorMessage%n%nAn error occurred while starting or stopping the memcached daemon on port %p with options %o: %e%n%aStatsMessage%n%nCurrent number of clients: %cCurrent memory usage: %mCurrent number of items: %iMax number of items: %MItems per slab: %sNumber of slabs: %rNumber of threads: %tTotal memory allocated: %ATotal number of requests served: %RTotal number of bytes read from network: %BTotal number of bytes written to network: %WTotal number of operations performed: %OAverage response time in microseconds: %yAverage latency in microseconds: %LAverage queue length in requests: %qAverage item size in bytes: %zCurrent time elapsed since server start: %TServer uptime in seconds: %Uptime in days, hours, minutes and seconds since server start: %DDays since last access: %ALast access time as a Unix timestamp (seconds since Jan 4 1970): %LLast command received from client: %CLast command sent to client: %SLast client who issued a command received a reply: %RLast client who requested an item received it: %QLast client who requested an item did not receive it due to lack of space: %HLast client who requested an item did not receive it due to an error: %ELast client who requested an item did not receive it due to a full cache: %FLast client who requested an item did not receive it due to a redirection error: %GLast client who requested an item did not receive it due to a connection error: %HLast client who requested an item did not receive it due to a timeout error: %JLast client who requested an item did not receive it due to a version mismatch error: %KLast client who received a reply for a command is still connected: %NLast client who received a reply for a command disconnected after receiving it: %MLast client who received a reply for a command disconnected before receiving it: %LLast client who received a reply for a command disconnected immediately after sending it: %OLast client who received a reply for a command disconnected immediately before sending it: %PLast client who received a reply for a command disconnected immediately after sending it and before receiving it: %QLast client who received a reply for a command disconnected immediately after sending it and before receiving it and then reconnected immediately afterwards: %RLast client who received a reply for a command disconnected immediately after sending it and before receiving it and then reconnected immediately afterwards and then disconnected again immediately afterwards: %SLast client who received a reply for a command disconnected immediately after sending it and before receiving it and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and so on until the end of the log file or until the server is stopped: %TLast client who received a reply for a command disconnected immediately after sending it and before receiving it and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and then disconnected again immediately afterwards and then reconnected immediately afterwards and然后disconnect