寫一個支持cluster suite切換的應(yīng)用腳本

fuumax

一個CS的應(yīng)用程序腳本需要符合LSB標(biāo)準(zhǔn)，需要支持以下幾個參數(shù)

start                    start the service
stop                     stop the service
restart                 stop and restart the service if the service is already running, otherwise start the service
try-restart            restart the service if the service is already running
reload                  cause the configuration of the service to be reloaded without actually stopping and restarting the service
force-reload          cause the configuration to be reloaded if the service supports this, otherwise restart the service if it is running
status                   print the current status of the service

你可以在/etc/init.d/下找到一些系統(tǒng)自帶服務(wù)的啟動腳本，比如ftp什么的，一般情況下他們都可以直接使用在CS中

如果你想編寫一個第三方應(yīng)用程序的腳本，那么一個帶注釋的例子如下

1. #!/bin/bash
   
2. 
   
3. #
   
4. #  Copyright Red Hat Inc., 2002
   
5. #  Copyright Mission Critical Linux, 2000
   
6. #
   
7. #  This program is free software; you can redistribute it and/or modify it
   
8. #  under the terms of the GNU General Public License as published by the
   
9. #  Free Software Foundation; either version 2, or (at your option) any
   
10. #  later version.
    
11. #
    
12. #  This program is distributed in the hope that it will be useful, but
    
13. #  WITHOUT ANY WARRANTY; without even the implied warranty of
    
14. #  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    
15. #  General Public License for more details.
    
16. #
    
17. #  You should have received a copy of the GNU General Public License
    
18. #  along with this program; see the file COPYING.  If not, write to the
    
19. #  Free Software Foundation, Inc.,  675 Mass Ave, Cambridge,
    
20. #  MA 02139, USA.
    
21. #
    
22. #
    
23. #  Author: Gregory P. Myrdal <Myrdal@MissionCriticalLinux.Com>
    
24. #
    
25. 
    
26. #
    
27. # This file contains a template that you can use to create a script
    
28. # that will start, stop and monitor an application used in a cluster service.
    
29. #
    
30. 
    
31. #------------------------------------------------------------
    
32. # Variable definitions
    
33. #------------------------------------------------------------
    
34. 
    
35. MYNAME=$(basename $0)
    
36. 
    
37. # The clug utility uses the normal logging levels as defined in
    
38. # sys/syslog.h.  Calls to clulog will use the logging level defined
    
39. # for the Service Manager (clusvcmgrd).
    
40. 
    
41. LOG_EMERG=0        # system is unusable
    
42. LOG_ALERT=1        # action must be taken immediately
    
43. LOG_CRIT=2        # critical conditions
    
44. LOG_ERR=3        # error conditions
    
45. LOG_WARNING=4        # warning conditions
    
46. LOG_NOTICE=5        # normal but significant condition
    
47. LOG_INFO=6        # informational
    
48. LOG_DEBUG=7        # debug-level messages
    
49. 
    
50. #------------------------------------------------------------
    
51. # Start of execution
    
52. #------------------------------------------------------------
    
53. 
    
54. if [ $# -ne 2 ]; then
    
55.         echo "Usage: $0 {start, stop, status} service_name"
    
56.         exit 1
    
57. fi
    
58. 
    
59. action=$1                # type of action, i.e. 'start', 'stop' or 'status'
    
60. svcName=$2                # name of the service
    
61. 
    
62. #
    
63. # Record all output into a temp file in case of error
    
64. #
    
65. exec > /tmp/$MYNAME.$action.log 2>&1
    
66. 
    
67. clulog -s $LOG_DEBUG "In $0 with action=$action, svcName=$svcName"
    
68. 
    
69. case $action in
    
70. 'start')
    
71.         clulog -s $LOG_INFO "Running user start script for service $svcName"
    
72.         #
    
73.         # <<< EDIT HERE: Add service start specfic code here >>>
    
74.         #
    
75.         ;;
    
76. 'stop')
    
77.         clulog -s $LOG_INFO "Running user stop script for service $svcName"
    
78.         #
    
79.         # <<< EDIT HERE: Add service stop specfic code here >>>
    
80.         #
    
81.         ;;
    
82. 'status')
    
83.         clulog -s $LOG_INFO "Running user status script for service $svcName"
    
84.         #
    
85.         # <<< EDIT HERE: Add service status specfic code here >>>
    
86.         #
    
87.         ;;
    
88. *)
    
89.         clulog -s $LOG_ERR \
    
90.                 "Unknown action '$action' passed to $svcName user script"
    
91.         exit 1                # return failure
    
92. esac
    
93. 
    
94. exit 0                        # return success
    

復(fù)制代碼

一個不符合lSB標(biāo)準(zhǔn)的腳本將導(dǎo)致，CS不停重起你的應(yīng)用程序，一個典型的例子就是httpd....oh my God !
詳情見bugzilla
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151104

希望能拋磚引玉，大家share出自己的腳本作品和實踐中的經(jīng)驗教訓(xùn)，共同提高

[ 本帖最后由 fuumax 于 2006-12-31 13:14 編輯 ]

haishen

暈, 這玩意就看實際應(yīng)用了, 沒有什么好說的 . 不過想apache, mysql什么的好像沒有狀態(tài)控制. 代碼要加上
status選項. 選項控制可以根據(jù)自己具體使用情況, 加以判斷做流程控制..  感覺這些例子沒有什么用處.

慧蘭于心

原帖由 haishen 于 2006-12-31 13:30 發(fā)表
暈, 這玩意就看實際應(yīng)用了, 沒有什么好說的 . 不過想apache, mysql什么的好像沒有狀態(tài)控制. 代碼要加上
status選項. 選項控制可以根據(jù)自己具體使用情況, 加以判斷做流程控制..  感覺這些例子沒有什么用處.

人家是好心總要支持一下嘛, 讓你這么折騰沒人愿來發(fā)貼了, 真是的,,,

haishen

噢  嘿嘿 ,  我錯了  
鼓勵  鼓勵,  不會讓我一句不著邊的話就打死吧, 也太脆弱了.......