Skip to Content
Last modified by Aaron Rosenzweig on 2011/05/09 01:46
From version 23.1
edited by Kieran Kelleher
on 2009/04/02 14:12
Change comment: There is no comment for this version
To version 28.1
edited by Kieran Kelleher
on 2008/11/23 19:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -108,8 +108,6 @@
108 108  
109 109  Now you need to restart wotaskd:
110 110  
111 -===== OS X Tiger 10.4 =====
112 -
113 113  {{code}}
114 114  
115 115  sudo systemstarter stop "WebObjects Services"
... ... @@ -119,32 +119,7 @@
119 119  
120 120  or
121 121  
122 -===== OS X 10.5 Leopard (where launchd is used to control wotaskd) =====
123 -
124 -{{code}}
125 -
126 -sudo launchctl stop com.apple.webobjects.wotaskd
127 -
128 -{{/code}}
129 -
130 -launchd should automatically start wotaskd again for you if configured properly.
131 -
132 -You can check for whether wotaskd is running as a launchd job by typing
133 -
134 -{{code}}
135 -
136 -sudo launchctl list | grep webobjects
137 -
138 -{{/code}}
139 -
140 -which will give something like this:
141 -
142 -{{code}}
143 -
144 -43 - com.apple.webobjects.wotaskd
145 -
146 -{{/code}}
147 -
120 +restart wotaskd and womonitor with launchctl if your WebObjects install launches that way.
148 148  (In 10.5 it appears to be necessary to launch with launchctl. See [[Running Monitor and wotaskd on Mac OS X 10.5 "client">>WO 5.4 Getting Started||anchor="javamonitor"]]
149 149  
150 150  == Finally, Configure your Application ==