[Pacemaker] Adding a timeout to an existing primitive

[Jody McIntyre]

I added a primitive to my cluster without setting a timeout:

root at trustcentric2:~# crm configure primitive PostgreSQL
ocf:trustcentric:postgresql
WARNING: PostgreSQL: default timeout 20s for start is smaller than the
advised 120
WARNING: PostgreSQL: default timeout 20s for stop is smaller than the
advised 120

I would now like to correct the timeout, since the defaults are too short.
How do I do this?  I found a brief section in one of the manuals:
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/index.html#s-operation-timeouts
but this is really unclear.  What id do I use in the <op>?  Can I simply
make one up?  I assume the name attribute matches the command in the OCF but
I'm not sure.

Also, perhaps more importantly, is there a way to do this without editing
XML?  I am happy to do this myself, but I don't think in-depth knowledge of
XML should be a requirement for any admins we hire!

I have attached an XML dump.

Thanks,
Jody
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110218/fca4a594/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: primitive_stuck.xml
Type: text/xml
Size: 10322 bytes
Desc: not available
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110218/fca4a594/attachment-0002.xml>