11-30-2009
I don't live in the US either, so, that's weird. But maybe Canada's close enough for them.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I have a mail server (sendmail) with SUNOS 5.5.1. Just recently it began to respond very slowly.
I used vmstat to check the performance data. Only interupt, system call and CPU context swiching are relatively high. Other statistics are normal, especially CPU utilization are very... (5 Replies)
Discussion started by: caoai
5 Replies
2. Solaris
Hi All,
There is a virtual user "ecoouk" which logs on to the server and runs some scripts. I want to know how much server performance can I gain if I put off all the scripts run by this user.
Please tell me how to analyse how much resources a specific user is using.
Regards,
Abhishek (3 Replies)
Discussion started by: max29583
3 Replies
3. Linux
Trying to connect to my companies VPN with vpnc but I keep getting an error that the target failed to respond. I run wireshark and see that my host sends out a few ISAKMP packets but gets no response and gives up.
Any ideas what can cause this to happen? Is there someway that UDP traffic could... (0 Replies)
Discussion started by: osulinux
0 Replies
4. UNIX for Dummies Questions & Answers
I have a Teradata Machine, using MP-RAS Unix, with a 1000 Intel Ethernet card and a Cisco switch.
If I configure the ethernet card and the switch to auto, so they negotiate to 1000, or configure the ethernet card and switch manually to 1000Full or 100Full, the velocity is very very low.
Only... (2 Replies)
Discussion started by: cuatrodos
2 Replies
5. UNIX for Dummies Questions & Answers
Hi Gurus of UNIX, I have a problem when I try to install a software VPN Cisco in Laptop (HP530).
I do the following procedures:
Part 2 - VPN Client Compilation
We will now set up the vpn client. As there is no official Cisco VPN Client for OpenSolaris X86 available, we will use vpnc.... (1 Reply)
Discussion started by: andresguillen
1 Replies
6. UNIX for Advanced & Expert Users
Working on a simple, half duplex network diagnostic that will run anywhere using nc and dd. Performance is symmetrical with sink and source nc processes open as a server:
nc -vkl 5000 > /dev/null &
cat /dev/zero | nc -vkl 5001 &
With this on the client:
nc host0 5001 | dd of=/dev/null... (0 Replies)
Discussion started by: netdrx
0 Replies
7. Cybersecurity
Hey everyone. I have a problem, but it may be my lack of understanding that is the cause. Ok so I attend a technical school, and needless to say there's a lot of wannabe hackers, pranksters and what not.
So from my laptop I'd like to connect to the wireless AP's around campus, but security is a... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies
8. Shell Programming and Scripting
Hi,
I am Shell script beginner.
I wrote a shell programming that will take each line of a file1 and search for it in another file2 and give me the output of the lines that do not exist in the file2.
I wrote it using do while nested loop but the problem here is its running for ever . Is there... (12 Replies)
Discussion started by: sakthisivi
12 Replies
LEARN ABOUT DEBIAN
explain_close_or_die
explain_close_or_die(3) Library Functions Manual explain_close_or_die(3)
NAME
explain_close_or_die - close a file descriptor and report errors
SYNOPSIS
#include <libexplain/close.h>
void explain_close_or_die(int fildes);
DESCRIPTION
The explain_close_or_die function is used to call the close(2) system call. On failure an explanation will be printed to stderr, obtained
from explain_close(3), and then the process terminates by calling exit(EXIT_FAILURE).
This function is intended to be used in a fashion similar to the following example:
explain_close_or_die(fildes);
fildes The fildes, exactly as to be passed to the close(2) system call.
Returns:
This function only returns on success. On failure, prints an explanation and exits.
SEE ALSO
close(2)
close a file descriptor
explain_close(3)
explain close(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2008 Peter Miller
explain_close_or_die(3)