ZMD, the ZENworks Management Daemon

/var/log/warn日志

Feb 25 19:33:59 ciq2000 su: (to oracle) root on /dev/pts/1             
Feb 25 20:02:28 ciq2000 zmd: ShutdownManager (WARN): Preparing to sleep...  
Feb 25 20:02:28 ciq2000 zmd: ShutdownManager (WARN): Going to sleep, waking up at 02/26/2017 19:22:24
Feb 25 20:30:01 ciq2000 /usr/sbin/cron[7224]: (root) CMD (su - oracle -c "/backup/script/delarch.sh")


ZMD, the ZENworks Management Daemon, allows users to manage \ software on their systems. \ Visit http://www.novell.com for more information.

根据描述，该服务是管理软件的，不知道是不是影响网络不通的原因，明天晚上看sleep后网络咋样。
环境：suse 10




官方文档；
https://www.novell.com/documentation/zlm72/lm7admin/data/b74nnf8.html
 zmd (8)
Name
zmd - The back-end daemon for the Novell? ZENworks? Linux Management agent.

Syntax
zmd [options]
Description

The zmd daemon performs software management functions on the ZENworks managed device, including updating, installing, and removing software, and performing basic queries of the device's package management database. Typically, these management tasks are initiated through the ZENworks Control Center or the rug, zen-installer, zen-updater, or zen-remover utilities, which means you should not need to interact directly with zmd.

The zmd daemon has built-in download interrupt support. If a download is interrupted, the zmd daemon resumes the download where it left off.

While making the HTTP requests, the zmd agent sets the HTTP User-Agent value to ZENworks Management Daemon/<version>, where <version> is a value as reported by the rug ping command.

The Device Black-Out feature of ZMD allows you to configure the following preferences:

    blackout-interval “<start_time> - <end_time>”: The time interval for which the device is to be locked. Specify the start time and end time in the HH:MM format, with hours in 24-hour format. For example, if the device is to be locked from 9 a.m. to 6 p.m., specify the time interval as 09:00-18:00.

    device-locked: Valid values are “True” and “False”. If the device-locked value is set to True, then zmd blocks install, removal, refresh, and register operations for packages and bundles. However, we recommend that you do not manually change the value of device-locked. The value is automatically set when you configure blackout-interval to specify the time interval when the device is to be locked. Depending on blackout-interval, the lock or unlock schedule is created and triggered. The lock or unlock schedule resets the device-locked value accordingly. If any refresh, bundle install, or bundle remove schedules are to be triggered when the device is locked, then these schedules are rescheduled to be triggered after the device is unlocked.

Options
Usage Options

-n , --non-daemon
    Do not run the daemon in the background.

-m , --no-modules
    Do not load any optional modules.

-r , --no-remote
    Do not load any optional modules.

--no-services
    Don't load the saved services.

Help Options
--help , -?
    Display the help information and exit.

Files
zmd.conf
   Configuration file. Options such as proxy and cache settings can be adjusted through this file directly or with the rug set command. The file is located in /etc/opt/novell/zenworks/zmd/ on SLES 9, OES 1, NLD, RHEL 3/4/5; and in /etc/zmd/ on SLES 10, SLED 10, and OES 2.

novell-zmd
    Initialization script. You should use this script to start and stop zmd, rather than running it directly. The file is located in /etc/init.d/ on SLES 9, SLES 10, SLED 10, NLD, RHEL, and OES.

zmd-messages.log
    Log file. The file is located in /var/opt/novell/log/zenworks/ on SLES 9, OES 1, NLD, and RHEL 3/4/5; and in /var/log/ on SLES 10, SLED 10, and OES 2.

zmd
    Cached information from servers. The directory is located in /var/opt/novell/zenworks/cache/ on SLES 9, OES 1, NLD, and RHEL 3/4/5; and in /var/cache/ on SLES 10, SLED 10, and OES 2.

initial-configuration
    URL for the supported services that zmd registers at initial startup. You can provide all the options that you would have otherwise used from rug for registration. The file is located in /etc/opt/novell/zenworks/zmd/ on SLES 9, OES 1, NLD, and RHEL 3/4/5; and in /etc/zmd/ on SLES 10, SLED 10, and OES 2.

Examples
This program normally runs as root.
/etc/init.d/novell-zmd start
    Runs the program in the standard way.

/opt/novell/zenworks/sbin/zmd or /usr/sbin/zmd
    Runs the program directly.



网上搜到为数不多的一个参考，先留着。

http://www.cnblogs.com/wanyakun/archive/2011/10/31/2230856.html


suse64x2:/var/log # cat /etc/zmd/zmd.conf
[Advanced]
run-transaction-test=False
security-level=signature

[Server]
bind-ip=127.0.0.1
refresh-interval=86400
remote-enabled=false
require-verified-certs=True

[Debug]
log-soap-xml=False
log-exception-traces=False


注意看上文中的86400，86400=60*60*24，也就是一天的秒数，所以才会一天出现一次sleep，所以打开YAST > system > services 然后将Novell zmd设置成disable。
这家伙反正是这样搞定了，明天去公司，我也这样设置下吧，最起码日志中不应该再出现 zmd: ShutdownManager (WARN): Preparing to sleep…