8 More Discussions You Might Find Interesting
1. Solaris
Solaris terminal responding very slow .. we have recently put a T3 hardware in to production , the applications running are it are perfectly and no complaints from user ..but when i ssh to the server ... the terminal response is very very slow .. it takes 3 seconds to show the character i type ..... (3 Replies)
Discussion started by: skamal4u
3 Replies
2. Post Here to Contact Site Administrators and Moderators
Hi,
I am experiencing slow response of unix.com from past 3-4 days.
like-
- most of the time the page does not reload instantly (when I do a manual reload from browser)
- not able to view graphics. ( displays only text).
- when posting into forum, the page gets stuck for considerably long... (6 Replies)
Discussion started by: clx
6 Replies
3. AIX
Hi All.
We are using AIX 5.3 ML9. There is 1 Gig NIC installed on two servers (Primary and Secondary) with Full Duplex Mode. We have scheduled a cronjob to copy the backup from primary to secondary thru FTP on WAN. The total data size is 15 GB and it took 9 Hours and 18 Mins with transfer rate... (6 Replies)
Discussion started by: lodhi1978
6 Replies
4. IP Networking
I have 20 servers I installed an application to that is returning message " wrong dispatcher or port " when starting agents. They all have the same dispatcher ip and going through the same port number. After verifying there are no application issues, we figured it was firewall related. The Firewall... (1 Reply)
Discussion started by: HFJ
1 Replies
5. Emergency UNIX and Linux Support
Hi,
My application runs on AIX, and clients complain of 3am slowdowns. This seems to have increased in the recent past.
Can someone guide me what are the various things that I need to be looking at on he AIX box, that could be causing slowdowns.
Thanks in Advance. (4 Replies)
Discussion started by: ggayathri
4 Replies
6. IP Networking
My company has a private network, including a Apache web server (Linux) and some WinXP machines. The web server had been configured to use mod_proxy to connect to window update site via another company proxy server. It works for few years.
Recently, some parties had setup a DNS server on the... (2 Replies)
Discussion started by: donaldfung
2 Replies
7. UNIX for Dummies Questions & Answers
Dear guys,
I don't know the response of a for loop in this situation:
suppose that file1 is an empty file.
and i make a for loop as :
for i in `cat file1`
What will be the response of the for loop:
1- will an error message apear
2- or the for loop simply will not run,and it will escape... (2 Replies)
Discussion started by: marwan
2 Replies
8. UNIX for Advanced & Expert Users
Hi all,
If I give ls , it lists files in 1 second.
It I give ls -l , it takes 8 seconds
There are only 55 files in the directory.
Any explanation?
Thanks
Wilson (4 Replies)
Discussion started by: geraldwilson
4 Replies
LEARN ABOUT CENTOS
wbemexec
wbemexec(1) wbemexec(1)
NAME
wbemexec - submit a CIM operation request to a CIM Server
SYNOPSIS
wbemexec [ -h hostname ] [ -p portnumber ] [ -v httpversion ]
[ -m httpmethod ] [ -t timeout ] [ -u username ]
[ -w password ] [ -s ] [ --help ] [ --version ]
[ inputfilepath ]
DESCRIPTION
The wbemexec command provides a command line interface to a CIM Server. The input to the command consists of a CIM request encoded in XML.
The request is submitted to the CIM Server for execution. If the HTTP response from the CIM Server contains a status code of 200 (OK), the
result returned to stdout is the CIM response encoded in XML. Otherwise, the result returned to stdout is the HTTP response. Some types
of invalid XML requests (e.g. missing PROTOCOLVERSION attribute or missing NAME attribute) are detected by wbemexec, and result in an error
message from wbemexec. Other invalid XML requests (e.g. invalid CIMVERSION attribute value or missing XML version), are detected by the
CIM Server, and result in an HTTP response, containing a non-Success status code, such as 501 (Not Implemented) or 400 (Bad Request).
By default, the request is sent as an HTTP/1.1 request, using the HTTP M-POST method, and wbemexec waits 20000 milliseconds (20 seconds),
then times out if a response hasn't been received. Input is read from stdin, if no input file is specified.
By default, the operation is executed on the local host. wbemexec first attempts to connect to the CIM Server on the default port for the
wbem-http service, and if that fails, another attempt is made on the default port for the wbem-https service.
Options
wbemexec recognizes the following options:
-h hostname Connect to the CIM Server on the specified host. If this option is not specified, wbemexec connects to the local
host.
--help Display command usage information.
-m httpmethod Use the specified HTTP method for the request. The method must be "POST" or "M-POST".
-p portnumber Connect to the CIM Server on the specified port number. If this option is not specified, wbemexec connects to the
default port for the wbem-http service, or if the -s option is specified, to the default port for the wbem-https ser-
vice.
-s Enable the use of the SSL protocol between and the CIM server. The -s option should be specified if the CIM Server
on the specified hostname/portnumber expects clients to connect using HTTPS.
-t timeout Wait the specified number of milliseconds on sending a request, before timing out if no response has been received.
The timeout value must be an integer value greater than 0.
-u username Connect as the specified R username . If username is not specified, the current logged in user is used for authenti-
cation. This option is ignored if neither hostname nor portnumber is specified.
-v httpversion Use the specified HTTP version for the request. The version must be "1.0" or "1.1". The 1.0 version may not be
specified if the M-POST method is specified.
--version Display CIM Server version.
-w password Authenticate the connection using the specified password . This option is ignored if neither hostname nor portnumber
is specified. WARNING: A password should not be specified on the command line on a multi-user system, since command-
line options are typically world-readable for a short window of time. If the remote host requests authentication and
this option is not specified, wbemexec will prompt for the password. (See cimconfig (1) for information on configur-
ing the CIM Server.)
EXIT STATUS
When an error occurs, an explanatory error message is written to stderr and an appropriate value is returned. The following exit values
are returned:
0 Success
1 Error
USAGE NOTE
The wbemexec command requires that the CIM Server is running.
EXAMPLES
Submit an XML request contained in the file cimrequest.xml to the CIM Server running on the local host on the default port:
wbemexec cimrequest.xml
Submit an XML request contained in the file cimrequest.xml to the CIM Server running on the host hpserver on port 49152, using the username
guest and password guest for authentication:
wbemexec -h hpserver -p 49152 -u guest -w guest cimrequest.xml
SEE ALSO
cimserver(1), cimconfig(1).
STANDARDS CONFORMANCE
wbemexec: CIM Operations over HTTP 1.0, Representation of CIM in XML 2.0
wbemexec(1)