Well, you are staring at the low graphics message but there is no response from the keyboard. The mouse may move but clicking is a waste of time. Best thing is to find another computer and ssh into the stricken box.
Next, we reconfigure so that the NVidia module gets rebuilt. Now, this is total overkill but it will work ...
sudo dpkg --configure -a
reboot and, hopefully, everything will be fine.
Monday, 13 December 2010
Wednesday, 31 March 2010
How to get ClearQuest 7.1.1 running on SLES/SLED11
Well, rational themselves says it won't work, but I got it to.
Make sure you have the update repositories added (you may need to add 11.1 repositories).
Update to latest firefox by adding mozilla repository
Make sure you have the update repositories added (you may need to add 11.1 repositories).
Update to latest firefox by adding mozilla repository
| zypper addrepo --refresh http://download.opensuse.org/repositories/mozilla/openSUSE_11.1/ mozilla
remove existing firefox zypper remove firefox
Install new one (update won't work which is why we remove first) zypper install mozilla:MozillaFirefox
This will not only give you firefox 3.6 but also update to a version of xulrunner which will work with CQ 7.1.1
Add the following to /opt/ibm/RationalSDLC/clearquest/rcp/configuration/config.ini
org.eclipse.swt.browser.XULRunnerPath=/usr/lib64/xulrunner-1.9.2
Or what ever the xulrunner is for 1.9.2. 1.9.0 and old 1.9.1 won't work!
Add the same line to /opt/ibm/RationalSDLC/clearcase/RemoteClient/configuration/config.ini to get clearcase remote client to work also!
|
Thursday, 18 December 2008
How to use curl to post a SOAP message
Sometimes, it is necessary to send a SOAP request to your web service to test
something out. There are multiple ways to do this - XMLSpy, socat,
netcat etc. but these are sometimes only available on development environments and not on machines where you might actually have to test something out.
That's when we can use curl to do this for us.
For the sense of this post, curl was the only network tool I had at my disposal to do this job but it's pretty handy.
First off, we need a sample SOAP message in a file. We can use curl to deal with the HTTP headers, so we only need the main body of data.
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
..................
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Let's say we store this in soap.req
We can then call our service like this :-
curl -d@soap.req http://someservice:8766
and see the result.
something out. There are multiple ways to do this - XMLSpy, socat,
netcat etc. but these are sometimes only available on development environments and not on machines where you might actually have to test something out.
That's when we can use curl to do this for us.
For the sense of this post, curl was the only network tool I had at my disposal to do this job but it's pretty handy.
First off, we need a sample SOAP message in a file. We can use curl to deal with the HTTP headers, so we only need the main body of data.
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
..................
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Let's say we store this in soap.req
We can then call our service like this :-
curl -d@soap.req http://someservice:8766
and see the result.
Well, the title says it all. If only I had started this 20 years ago, I would have had a fantastic record of my knowledge growth (and demise) from the start of my IT career to the present. Pretty much all of my wrangling with Linux from its inception would have been here, but there is no point in dwelling on things that haven't happened. I've got to start somewhere ...
Subscribe to:
Posts (Atom)