11-06-2002
it works.
thank you very much
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am curious about HUP..... kill -HUP pid
What exactly does it do?? Does it stop the process and restart it from the beginning or from where it stopped? Thanks (6 Replies)
Discussion started by: jwbrown
6 Replies
2. SuSE
everytime I try to start SWAT using : www.localhost:901, it takes me to goggle the search engine. IM still new in the linux world and Im a bit confussed now. any help would be great. Im currently running redhat linux fedora. (5 Replies)
Discussion started by: keliy1
5 Replies
3. Solaris
Hi,
I had define swat in /etc/services, in /etc/inet/inetd.conf. When I start swat http://localhost:901 I receive the follow message: ld.so.1: swat: fatal: libiconv.so.2: open failed: No such file or directory
Then I restart the system and the same message is comming. The swat is only... (2 Replies)
Discussion started by: MuellerUrs
2 Replies
4. Linux
Hi All,
I modified /etc/syslog.conf and execute kill -HUP syslogd_PID. There's nothing changes on the PID when I did ps -ef|grep syslogd. It's the same. Do you think it restarted the process of syslogd?
Thanks in advance. (3 Replies)
Discussion started by: itik
3 Replies
5. UNIX for Advanced & Expert Users
We encountered an issue in our project while using the Interix UNIX (SFU 3.5) and explained our query below. We would be happy if anybody helps us to troubleshoot the problem J
In our code the trapping signal for all signals like HUP, INT, QUIT, ILL, TRAP, ABRT, EXCEPT, etc., is initialized in... (4 Replies)
Discussion started by: RAMESHPRABUDASS
4 Replies
6. UNIX for Dummies Questions & Answers
Hello - I need to know the detail of HUP and SEGV.
I know HUP is Hangup and can be use to kill a Unix login session remotely by sending a hangup signal to the process running the login session.
Could someone tell me in detail prupose of HUP and SEGV (segmentation violation)?
I need to... (1 Reply)
Discussion started by: namasteall2000
1 Replies
7. Solaris
Hi,
I'm trying to provide "/usr/bin/kill -HUP" command to one of the user using sudo file. I have configured sudo as following:
$cat /etc/sudoers
User_Alias AA=conadmin
Cmnd_Alias KILL1=/usr/bin/kill -HUPAA ALL=NOPASSWD:KILL1
When I login as the user and execute 'sudo -l' command, it... (2 Replies)
Discussion started by: mohzub
2 Replies
8. Red Hat
Hi,
I have installed RHEL 5.2 for a specific reason.
Anyway I would really like to use SWAT to administer Samba. Samba is currently installed and working almost successfully however SWAT would make life a bit easier.
I have tried rpm -ivh samba-swat but it can't find the file. ... (1 Reply)
Discussion started by: drag0n
1 Replies
9. Red Hat
Hi,
I have been trying to install SWAT on redhat 6 for samba4. The samba server was installed by another administrator but not swat. Please find output of yum install samba-swat in the attached file (2 Replies)
Discussion started by: p2bas
2 Replies
AIC(4) BSD/i386 Kernel Interfaces Manual AIC(4)
NAME
aic -- Adaptec AIC-6260 and AIC-6360 SCSI driver
SYNOPSIS
device aic
In /boot/device.hints:
hint.aic.0.at="isa"
DESCRIPTION
The aic driver provides support for the Adaptec AIC-6260 and AIC-6360 SCSI controller chips. Many systems that use these controller chips do
not have a boot ROM and therefore cannot be booted from.
HARDWARE
The adapters supported by the aic driver include:
o Adaptec AHA-1505 (ISA)
o Adaptec AHA-1510A, AHA-1510B (ISA)
o Adaptec AHA-1520A, AHA-1520B (ISA)
o Adaptec AHA-1522A, AHA-1522B (ISA)
o Adaptec AHA-1535 (ISA)
o Creative Labs SoundBlaster SCSI host adapter (ISA)
o Adaptec AHA-1460, AHA-1460B, AHA-1460C, AHA-1460D (PC Card)
o Adaptec AHA-1030B, AHA-1030P (PC98)
o NEC PC-9801-100 (PC98)
SEE ALSO
aha(4), ahb(4), ahc(4), cd(4), ch(4), da(4), intro(4), sa(4)
BUGS
The driver does not work well with multiple devices on the SCSI bus. The driver works well with devices like CDROMs and Tape drives. The
driver works not so well with disk drives. The PC Card version appears to work better than the ISA version, but that may be due to differing
levels of testing of the devices.
BSD
November 8, 2003 BSD