02-19-2004
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
1.I was trying to use Exceed to run Solaris "openwin" on my Windows 95. I got an error :
/usr/openwin/bin/openwin &
28522
$
/dev/fb: No such file or directory
Graphics Adapter device /dev/fb is of unknown type
Fatal server error:
InitOutput: Error loading module for /dev/fb
Does... (1 Reply)
Discussion started by: b5fnpct
1 Replies
2. Post Here to Contact Site Administrators and Moderators
Hi Gents,
I have downloaded Sol 8 2/04 from Sun's web page and I have tried to install it into a V890. I can boot from a CD 1of 2 without any problem.
After the selection of the language and the Locale, the TWM (Sol Install Console window) cannot starts up. The following are the errors... (0 Replies)
Discussion started by: mmakhol
0 Replies
3. HP-UX
:confused:
I have an K580 HP server.
All I did was change the IP address on the NIC and now I can't telnet into it.
I can ping, but no telnet.
Also, it won't boot if the console monitor is plugged in.
ANY IDEAS??? (1 Reply)
Discussion started by: ncmurf00
1 Replies
4. UNIX for Dummies Questions & Answers
I have a client who is using Solaris 8 and on login the system tris to open windows but then generates the following error
failed to open /usr/openwin/AcceleratedX/etc/Siteinfo
Fatal Server error
Failed to configure the xserver
Help Please!
Thanks (0 Replies)
Discussion started by: alvinc77
0 Replies
5. UNIX for Dummies Questions & Answers
Solaris 10 on an Ultra 45, there are two serial ports (com A and B) And I need to be able to use an old serial trackball mouse in the openwin dt enviornment. Do I have any options? Even if I have to buy an external device for conversion? Want to configure openwin to use an old serial pointer device... (0 Replies)
Discussion started by: ajp7701
0 Replies
6. UNIX for Advanced & Expert Users
I am running Solaris 10. Occasionally, my id gets loked. I want to know who/which rougue process locked it.
How do I find out?
Thanks,
KNK (9 Replies)
Discussion started by: nkamatam
9 Replies
7. Solaris
Hi all!
Solaris 10.
Why did X-server stop to read OWfontpath?
Any suggestions.
Thanks. (0 Replies)
Discussion started by: wolfgang
0 Replies
8. UNIX for Dummies Questions & Answers
Here's the story:
I had an LaCie Internet Space (1TB)... Recently the network (or software)
functions of the device just died... I tried to access it via different routers,
checking UTP, tried everything possible to rule out physical damage to
components.
Then i got the disk out of its... (2 Replies)
Discussion started by: SentinelX
2 Replies
9. Hardware
I have several applications locked to Solaris 8 (and older) and have been very happy with my Sparcs and Ultras but am getting tinnitus problems from fans and disks.
Any tips on a quiet thin client (with decent graphics, not video or gaming level but 24bit and multi monitor would be useful) that... (0 Replies)
Discussion started by: batchman
0 Replies
10. UNIX for Beginners Questions & Answers
Hi.
I have a Microsystems SunBlade 150
shell# cat /etc/release
Solaris 8 2/02 s28s_u7wos_08a SPARC
shell# uname -a
SunOS HOSTNAME 5.8 Generic_108528-14 sun4u sparc SUNW,Sun-Blade-100
shell# prtconf -F
/pci@1f,0/SUNW,m64B@13:m640
When I join to the only account the server try to... (5 Replies)
Discussion started by: siegroup
5 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)