10 More Discussions You Might Find Interesting
1. Fedora
Okay, I'm fairly green at Fedora, but it has worked like a gem until now. On startup I get a screen that says this:
Booting 'Fedora (3.6.11-4.fc16.x86_64)'
Loading Fedora (3.611-4.fc16.x86_64)
Loading initial ramdisk ....
_Fedora-16-x86_6: Unexpected inconsistency; run fsck manually.
... (6 Replies)
Discussion started by: Anchorsteamer
6 Replies
2. Red Hat
Hi, I am using redhat enterprise 5.7 have installed vsftpd successfully but every time I try to start the service it comes up with FAILED. Here is the contents of the vsftpd.conf file:
# Allow anonymous FTP? (Beware - allowed by default if you comment this out).
anonymous_enable=YES
#
#... (3 Replies)
Discussion started by: titley100
3 Replies
3. AIX
Hi,
My NFS does not work till I start HACMP. The NFS service is indeed started when server starts. But it is not in active state, when I use lssrc to check NFS services' status I find they are all in inoperative status. But after I start HACMP (smitty clstart), all NFS services become active... (4 Replies)
Discussion started by: qiulang
4 Replies
4. Solaris
if anyone can help me here I will be in debt eternaly. I'm in a spot here fearing for my job.
I tried to install a new scsi array on our E5500. I powered it down correctly, removed the terminator, connected the array and powered it on. It was taking so long to come up I freaked out and powered... (3 Replies)
Discussion started by: NewSolarisAdmin
3 Replies
5. Red Hat
im running rh 9 on my vmware, i tryed changing the graphics card mode
to resize the desktop, after restarting i get a message X Server cannot start.
then it takes me to the consol screen to log on, "im new to using linux as of last night"
It would be helpfull if anyone can help me resolve... (4 Replies)
Discussion started by: aoteg
4 Replies
6. Solaris
Hi.
I got this message in our sun station and it stuck
Setting default IPv4 interface for multicast: add net 224.0/4: gateway pecsun22
but i can still telenet the station...
who could i fix this..
appreciate your help (7 Replies)
Discussion started by: eykyn17
7 Replies
7. SuSE
I recently installed SLES 10 on an x86 64bit blade server. I then installed vsftpd from the suse cds through network services; however after configuring the vsftpd.conf file, the server fails to start:
# /etc/init.d/vsftpd start
Starting vsftpd startproc: exit status of parent of... (5 Replies)
Discussion started by: dave521
5 Replies
8. UNIX for Dummies Questions & Answers
After I log ino the machine, a window pops up indicating that I should check that the HOSTNAME is the same in these three files
/etc//rc.configd/netconf
/etc/hosts
/var/adm/inetd.sec
How do I change the hostname in these files?
Thanks,
Mike h (1 Reply)
Discussion started by: hutchin
1 Replies
9. Solaris
Hi
Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say... (19 Replies)
Discussion started by: dcshungu
19 Replies
10. UNIX for Dummies Questions & Answers
Backup Exec Agent won't start....
Question: Has anyone had any previous experience working with Backup exec for Unix? I'm running SCO Openserver 5.0.5 and Backup Exec agent Version 5.01 Revision 5.032 Basically, these are the commands I'm issueing and here is the output.
# cd etc
# cd... (1 Reply)
Discussion started by: PatMcCoy
1 Replies
tt_message_send_on_exit(library call) tt_message_send_on_exit(library call)
NAME
tt_message_send_on_exit -- set up a message to send upon unexpected exit
SYNOPSIS
#include <Tt/tt_c.h>
Tt_status tt_message_send_on_exit(
Tt_message m);
DESCRIPTION
The tt_message_send_on_exit function requests that the ToolTalk service send this message if the process exits unexpectedly. The message
is sent to the ToolTalk service, which queues the message internally until either of two events occur:
1. The procid that sent the tt_message_send_on_exit message to the ToolTalk service calls tt_close(3). In this case, the queued message
is deleted.
2. The connection between the ttsession(1) server and the process that sent the tt_message_send_on_exit message to the ToolTalk service
is broken; for example, if the application has crashed.
In this case, the ToolTalk service matches the queued message to its patterns and delivers it in the same manner as if the process had sent
the message normally before exiting.
If a process sends a normal termination message but exits without calling tt_close(3), both the normal termination message and the on_exit
message are delivered.
The m argument is the opaque handle for the message involved in this operation.
RETURN VALUE
Upon successful completion, the tt_message_send_on_exit function returns the status of the operation as one of the following Tt_status val-
ues:
TT_OK The operation completed successfully.
TT_ERR_ADDRESS
The specified Tt_address is invalid.
TT_ERR_CLASS
The specified Tt_class is invalid.
TT_ERR_FILE
The specified file does not exist or it is inaccessible.
TT_ERR_NOMP
The ttsession(1) process is not running and the ToolTalk service cannot restart it.
TT_ERR_OBJID
The objid passed to the ToolTalk service does not reference an existing object spec.
SEE ALSO
Tt/tt_c.h - Tttt_c(5), tt_close(3).
tt_message_send_on_exit(library call)