05-15-2012
I think you need to post the difference between two samples over a given reasonable period of time.
Depending on what network kit this server is plugged into, auto-negotiation should be avoided. It usually needs turning off on the server and the LAN port. Similarly anywhere where network components are cascaded.
It looks like auto-negotiation is off on your server.
Last edited by methyl; 05-15-2012 at 12:44 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What characters can't be used with a mkdir? Any limits on length of name?
Thank you,
Randy M. Zeitman
http://www.StoneRoseDesign.com (12 Replies)
Discussion started by: flignar
12 Replies
2. UNIX for Dummies Questions & Answers
I am trying to use the csplit file on a file that contains records that have more than 2048 characters on a line. The resultant split file seems to ignore the rest of the line and I lose the data.
Is there any way that csplit can handle record lengths greater than 2048?
Thanks (0 Replies)
Discussion started by: ravagga
0 Replies
3. UNIX for Dummies Questions & Answers
I would like to set my minimum password length to on Linux and AIX.
However, doing this normally would only make it so newly added users will be affected by this. I would like for when I make this change, it either truncates everyone elses password, or prompts them to change it to 8+ characters.... (2 Replies)
Discussion started by: syndex
2 Replies
4. Solaris
Is there a limit to the number of LUNS that can be concatenated using Solaris Volume manager with Soft partitions?
I have worked with some AIX admins in the past and there was such a limitation therefore limiting the size the filesystem could grow to.
Is there such a limitation in Solaris 9... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
5. UNIX and Linux Applications
I'm running a simulation (programmed in C) which makes calls to gnuplot periodically to plot data I have stored.
First I open a pipe to gnuplot and set it to multiplot:
FILE * pipe = popen("gnuplot", "w");
fprintf(pipe, "set multiplot\n");
fflush(pipe);
(this pipe stays open until the... (0 Replies)
Discussion started by: sedavidw
0 Replies
6. Red Hat
Hi,
I need a documentation about limitations on the linux partition. On how many primary and extended I could create. And also on different type of storage, how many big capacity I can create.
Thanks. (3 Replies)
Discussion started by: itik
3 Replies
7. Shell Programming and Scripting
I've building a bunch of bash scripts, and am thinking about "converting" to perl, and have a couple questions first:
1. Is there anything bash will do that perl won't?
2. How steep is the learning curve?
3. If perl's more powerful, why?
4. I've built a small app in python, which seemed nice,... (18 Replies)
Discussion started by: unclecameron
18 Replies
8. Shell Programming and Scripting
As part of a quiz assigned during my unix class I was asked to write a program to ask for a file name, print read errors, and "reverse elements in a list."
I used the 'tac' command in my solution, however, I was then lectured for 5 min about the "limitations" of the 'tac' command and how a 'for'... (6 Replies)
Discussion started by: 127.0.0.1
6 Replies
9. Solaris
Hi,
I recently started working with Solaris, and what I noticed is that a lot of commands I used to regularly use don't work, like sed -i and grep -r. I have found work arounds for these problems though but it's a pain in the ass.
I'm just wondering why they decided not to include these handy... (4 Replies)
Discussion started by: Subbeh
4 Replies
10. UNIX for Beginners Questions & Answers
Guys: I have a customer using the 'pdftotext' utility under Linux. PDFs are received via email, converted to text, etc. and it has worked nicely for years. They received a PDF from a customer and the utility will not read it. The text file is created but it's either empty or has 1-2 bytes of... (23 Replies)
Discussion started by: kenlenard
23 Replies
LEARN ABOUT DEBIAN
sasl_client_step
sasl_client_step(3) SASL man pages sasl_client_step(3)
NAME
sasl_client_step - Perform a step in the authentication negotiation
SYNOPSIS
#include <sasl/sasl.h>
int sasl_client_step(sasl_conn_t *conn,
const char *serverin,
unsigned serverinlen,
sasl_interact_t ** prompt_need,
const char ** clientout,
unsigned * clientoutlen);
DESCRIPTION
sasl_client_step() performs a step in the authentication negotiation. It returns SASL_OK if the whole negotiation is successful and
SASL_CONTINUE if this step is ok but at least one more step is needed. A client should not assume an authentication negotiation is success-
ful just because the server signaled success via protocol (i.e. if the server said ". OK Authentication succeeded" in IMAP sasl_client_step
should still be called one more time with a serverinlen of zero.
If SASL_INTERACT is returned the library needs some values to be filled in before it can proceed. The prompt_need structure will be filled
in with requests. The application should fulfill these requests and call sasl_client_start again with identical parameters (the prompt_need
parameter will be the same pointer as before but filled in by the application).
conn is the SASL connection context
serverin is the data given by the server (decoded if the protocol encodes requests sent over the wire)
serverinlen is the length of serverin
clientout and clientoutlen is created. It is the initial client response to send to the server. It is the job of the client to send it over
the network to the server. Any protocol specific encoding (such as base64 encoding) necessary needs to be done by the client.
RETURN VALUE
sasl_client_step returns an integer which corresponds to one of the following codes. SASL_CONTINUE indicates success and that there are
more steps needed in the authentication. SASL_OK indicates that the authentication is complete. All other return codes indicate errors and
should either be handled or the authentication session should be quit.
CONFORMING TO
RFC 4422
SEE ALSO
sasl(3), sasl_callbacks(3), sasl_errors(3), sasl_client_init(3), sasl_client_new(3), sasl_client_start(3)
SASL
10 July 2001 sasl_client_step(3)