02-21-2019
Linux SuSE SLES 8 error..unable to issue shutdown command
the only way we can power off is if we actually press power button on server. Running on HP DL-G4. from root, when we issue command it just returns to root prompt.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi,
In solaris, psrinfo gives number of cpu in use/online and so on.
What is the equivalent command for "psrinfo" in Suse Linux ?
Thx (3 Replies)
Discussion started by: braindrain
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
In SUSE SLES 10 SP2 where are the software repositories located? In CENTOS they are in /etc/yum.repositories or something like that. What does SLES use? (1 Reply)
Discussion started by: mojoman
1 Replies
3. SuSE
Can anyone give me a little clue on why the hard drive cache read timings on sles 9 is better then sles 11? The same hardware was used in both test. I even deleted the ata_generic module from initrd.
The speed difference is 10MB vs 5 MB
Thanks (1 Reply)
Discussion started by: 3junior
1 Replies
4. Linux
Hi Team,
I have joined the Suse Linux Server in my domain. I am not able update the DNS but I am able to join the domain. net ads testjoin gives me Join ok.
even net ads dns register -P results to DNS update failed.
wbinfo -u and wbinfo -g also not working.
Samba Configuration:
... (1 Reply)
Discussion started by: naree
1 Replies
5. SuSE
Hello All,
I'm using my Ubuntu 10.04 client connected via SSH to a SuSE Linux server (SuSE Linux Enterprise Server 11 (x86_64) version 11 patchlevel=1).
I'm trying to run an install of WebSphere Portal but can't seem to be able to run the GUI installer.
Running xclock as root returns this... (7 Replies)
Discussion started by: kartrait
7 Replies
6. UNIX and Linux Applications
The existing .pc (pro *C) file is running successfully in UNIX. But when Iam trying to compile this same file in LINUX using proc iname filename.pc, Iam getting an error, proc file not recognized.
Could someone help how to generate execute file from the proc*c file.
what are the prerequisites... (2 Replies)
Discussion started by: vikrambharat
2 Replies
7. High Performance Computing
We have a server with 160 hyper-threaded cpu's threads and 2Tb of RAM. I need to implement command line job queue and parallel thread usage for multiple user environment kindly suggest necessary tools to be installed.
I have understanding that sun grid engine like applications are available for... (0 Replies)
Discussion started by: vaibhavvsk
0 Replies
8. SuSE
Hello All,
I am new to use linux. I installed SUSE Linux Enterprise Server 11 (x86_64) trail version which is free for 60 days.
Now I want to again format the whole system and install the same OS again but its not happening.
I am trying with a bootable pen drive which has an .iso image of... (1 Reply)
Discussion started by: hunk_harsha
1 Replies
9. Shell Programming and Scripting
Hello,
I have a backup script that runs an rsync backup to an external drive. I use the script frequently on Windows and Linux and have installed it on a Mac. The script has an option to run shutdown after the backup has completed. Since backup can take hours to run, this is an option that is... (10 Replies)
Discussion started by: LMHmedchem
10 Replies
XKILL(1) General Commands Manual XKILL(1)
NAME
xkill - kill a client by its X resource
SYNOPSIS
xkill [-display displayname] [-id resource] [-button number] [-frame] [-all]
DESCRIPTION
Xkill is a utility for forcing the X server to close connections to clients. This program is very dangerous, but is useful for aborting
programs that have displayed undesired windows on a user's screen. If no resource identifier is given with -id, xkill will display a spe-
cial cursor as a prompt for the user to select a window to be killed. If a pointer button is pressed over a non-root window, the server
will close its connection to the client that created the window.
OPTIONS
-display displayname
This option specifies the name of the X server to contact.
-id resource
This option specifies the X identifier for the resource whose creator is to be aborted. If no resource is specified, xkill will
display a special cursor with which you should select a window to be kill.
-button number
This option specifies the number of pointer button that should be used in selecting a window to kill. If the word "any" is speci-
fied, any button on the pointer may be used. By default, the first button in the pointer map (which is usually the leftmost but-
ton) is used.
-all This option indicates that all clients with top-level windows on the screen should be killed. Xkill will ask you to select the
root window with each of the currently defined buttons to give you several chances to abort. Use of this option is highly discour-
aged.
-frame This option indicates that xkill should ignore the standard conventions for finding top-level client windows (which are typically
nested inside a window manager window), and simply believe that you want to kill direct children of the root.
CAVEATS
This command does not provide any warranty that the application whose connection to the X server is closed will abort nicely, or even abort
at all. All this command does is to close the connection to the X server. Many existing applications do indeed abort when their connection
to the X server is closed, but some can choose to continue.
XDEFAULTS
Button Specifies a specific pointer button number or the word "any" to use when selecting windows.
SEE ALSO
X(7), xwininfo(1), XKillClient and XGetPointerMapping in the Xlib Programmers Manual, KillClient in the X Protocol Specification
AUTHOR
Jim Fulton, MIT X Consortium
Dana Chee, Bellcore
X Version 11 xkill 1.0.3 XKILL(1)