02-14-2014
9 More Discussions You Might Find Interesting
1. AIX
We're having problems getting disconnected from AIX with our telnet sessions.
I can't ping the server when this happens, either. Other serves can be pinged at the same time.
This happens both at unix and within the database. Database locks remain when editing files. unix logins remain after... (0 Replies)
Discussion started by: e1lyons
0 Replies
2. IP Networking
hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies
3. AIX
I have intermec handheld device which is connecting to AIX Server on port 12431 or whatever. ( oracle application )
The handheld device connects for few seconds and then disconnects from the AIX server. Once it disconnects the handheld device automatically switches off.
Are there any... (2 Replies)
Discussion started by: filosophizer
2 Replies
4. Windows & DOS: Issues & Discussions
i am using Putty to do ssh to all the unix nodes that we have in our work environment. it is very strange that all my network connections will timeout quickly in 10 mins, it can either be a putty connection, sqlplus or toad. is there some setting that can help to prevent this. please let me know... (3 Replies)
Discussion started by: sudhiroracle
3 Replies
5. Programming
Hello everyone. Thanks for reading. I am using Ubuntu 7.04 to experience this problem:
I have written my own programs that communicate to eachother and I am having a hard time detecting a TCP socket disconnect when the remote side's computer has a power-failure (for example).
On the computer... (6 Replies)
Discussion started by: pjwhite
6 Replies
6. Programming
Hello,
I am able to establish a connection, and transfer data. Occasionally the receiving client will block in read(2) and stay that way until it is killed.
initial:
server: netstat -aveeopT
tcp 0 0 *:17398 *:* LISTEN server-user... (8 Replies)
Discussion started by: eoa
8 Replies
7. UNIX for Dummies Questions & Answers
Is there a way to have persistent terminal windows to redhat server across viewer disconnects? I can do that with the help of an extra MS Windows server and rdp, but is there a way of doing that without the Windows server?
Here's the scenario. I have multiple redhat servers (VMs) which have no... (3 Replies)
Discussion started by: ad101
3 Replies
8. SCO
I have inherited and SCO OpenServer Release 6 server. The clients connect using telnet to get to a proprietary database application for Service tickets. The issue I am currently having is that the connection just stops abruptly and you can see "telnet session terminated" on the terminal emulation... (22 Replies)
Discussion started by: sean6605
22 Replies
9. Solaris
Hi,
Sorry if this question has been asked before, however, I have tried looking in the forum (and google in general) and I haven't found an answer, so I thought I'd ask here.
I am trying to use a GUI application in Solaris 10. Normally I connect with a VPN then SSH and use Xming to... (2 Replies)
Discussion started by: John_sp
2 Replies
PANIC(9) BSD Kernel Developer's Manual PANIC(9)
NAME
panic -- Bring down system on fatal error
SYNOPSIS
#include <sys/types.h>
#include <sys/systm.h>
void
vpanic(const char *fmt, va_list ap);
void
panic(const char *fmt, ...);
DESCRIPTION
The panic() and vpanic() functions terminate the NetBSD system. The message fmt is a printf(3) style format string which is printed to the
console and saved in the variable panicstr for later retrieval via core dump inspection. A newline character is added at the end automati-
cally, and is thus not needed in the format string.
If a kernel debugger is installed, control is passed to it after the message is printed. If the kernel debugger is ddb(4), control may be
passed to it, depending on the value of ddb.onpanic. See options(4) for more details on setting ddb.onpanic. If control is not passed
through to ddb(4), a ddb(4)-specific function is used to print the kernel stack trace, and then control returns to panic().
If control remains in panic(), an attempt is made to save an image of system memory on the configured dump device.
If during the process of handling the panic, panic() is called again (from the filesystem synchronization routines, for example), the system
is rebooted immediately without synchronizing any filesystems.
panic() is meant to be used in situations where something unexpected has happened and it is difficult to recover the system to a stable
state, or in situations where proceeding might make the things worse, leading to data corruption/loss. It is not meant to be used in scenar-
ios where the system could easily ignore and/or isolate the condition/subsystem and proceed.
In general developers should try to reduce the number of panic() calls in the kernel to improve stability.
RETURN VALUES
The panic() function does not return.
SEE ALSO
sysctl(3), ddb(4), ipkdb(4), options(4), savecore(8), swapctl(8), sysctl(8)
BSD
September 29, 2011 BSD