02-18-2009
Usually kill -l will list all available signals on your system, but it's probably the TRAP signal (
description)
10 More Discussions You Might Find Interesting
1. Programming
signal in process communication:
I 'm a example in sun_unix that signal in process communication
It's here down but I only have freebsd in my machine.
how can i do the same in freebsd
eg:
#include <stdio.h>
#include <signal.h>
#include <unistd.h>
int
main( void ){
void... (2 Replies)
Discussion started by: a9711
2 Replies
2. UNIX for Advanced & Expert Users
Hi all,
How can a process be aware of the signals it handles. I looked at available signal API, but couldn't find any help.
If a process defines it own handler for a signal, the default handler for that signal becomes overridden.
I am interested in getting to know the... (2 Replies)
Discussion started by: bluehive
2 Replies
3. Programming
i am creating children processes using fork system call
every child i create goes to sleep for random time.
when child stops running how can i catch his signal and turminate the child (2 Replies)
Discussion started by: emil2006
2 Replies
4. Solaris
Rebuilding a server (T2000) from a flash archive I created on another server. Using a Solaris 10/08 DVD to boot from the was going to point it tot he flash archive and pull it over NFS. I've done this many times with success until now.
It initially boots off the DVD, you input the... (5 Replies)
Discussion started by: Probos
5 Replies
5. Programming
Hi all,
Does a background process send a signal to its parent when completed? If so, how might i capture this signal?
I'm trying to write shell in c so that when a background process finishes, it prints a message to the console.
Thanks in advance for any advice. (1 Reply)
Discussion started by: jmelai
1 Replies
6. Solaris
Hi,
I am pretty new to Solaris and am trying to upgrade from the OBP.
I go through the process of booting from the cdrom, entering all necessary information and running the upgrade. The system completes analysis and then fail with the
EXITING (caught signal 11) error
I believe that... (5 Replies)
Discussion started by: Seanliam
5 Replies
7. Emergency UNIX and Linux Support
Hello, everyone.
Here's a program:
pid_t pid = fork();
if (0 == pid) // child process
{
execvp ...;
}
I send a signal (such as SIGINT) to the parent process, the child process receive the signal as well as the parent process.
However I don't want to child process to receive the... (7 Replies)
Discussion started by: jackliang
7 Replies
8. Solaris
I get an error after the initializing screen. I am using a DVD/ROM to boot up the installation on a Dell Inspiron 1520. Segmentation fault - core dumped. I have tried to restart multiple times. Please help (1 Reply)
Discussion started by: Jimasaurus
1 Replies
9. Solaris
I created a new Virtual machine and was trying to install Solaris but keep getting this error.:confused:
EXITING (caught signal 11)
Type "install-solaris to restart"
Can't find anything on Google.
This is the iso image I am using "sol-10-u11-ga-x86-dvd"
Followed all the instructions on... (5 Replies)
Discussion started by: newborndba
5 Replies
10. Shell Programming and Scripting
Is it possible to continue after signal is caught and control goes to function specified in the trap statement? (3 Replies)
Discussion started by: Soham
3 Replies
URL(4) BSD Kernel Interfaces Manual URL(4)
NAME
url -- Realtek RTL8150L USB Ethernet driver
SYNOPSIS
url* at uhub?
urlphy* at mii?
DESCRIPTION
The url driver provides support for USB Ethernet adapters based on the Realtek RTL8150L USB-ether bridge chip.
The url driver supports the following adapters:
CompUSA USBKR100
GreenHouse GH-USB100B
Melco Inc. LUA-KTX
Sitecom LN013
For more information on configuring this device, see ifconfig(8).
DIAGNOSTICS
url%d: watchdog timeout A packet was queued for transmission and a transmit command was issued, however the device failed to acknowledge the
transmission before a timeout expired.
url%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring.
SEE ALSO
arp(4), mii(4), netintro(4), usb(4), ifconfig(8)
HISTORY
The url device driver first appeared in NetBSD 1.6.
AUTHORS
The url driver was written by Shingo WATANABE <nabe@nabechan.org>.
BSD
September 18, 2006 BSD