Not able understand logic and working Post: 303023124

2 More Discussions You Might Find Interesting

1. Solaris

Cant understand the File system working nature

Hi, We have a filesystem whose usage has gone above 81%, i tried to zip some files in the sub directories but the space is not released in the main file system. > df -h Filesystem size used avail capacity Mounted on /u01/app 5.8G 4.6G 1.2G 81% ...

2. Shell Programming and Scripting

Need to understand a couple of Shell Logic

Hi, I am trying what the following loop does : for i in XYZ do for j in M1 R1 R2 R3 do if then kList="" n=1 while do kList="$kList $n" let n++ done There are a couple of loop as mentioned above for R1.R2.R3.

LEARN ABOUT CENTOS

sasl_server_step

sasl_server_step(3)						  SASL man pages					       sasl_server_step(3)

NAME

       sasl_server_step - Perform a step in the authentication negotiation

SYNOPSIS

       #include <sasl/sasl.h>

       int sasl_server_step(sasl_conn_t *conn,
			   const char *clientin,
			   unsigned clientinlen,
			const char ** serverout,
			   unsigned * serveroutlen);

DESCRIPTION

       sasl_server_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.

       conn is the SASL connection context

       clientin is the data given by the client (decoded if the protocol encodes requests sent over the wire) clientinlen is the  length  of  cli-
       entin

       serverout and serveroutlen are set by the library and should be sent to the client.

RETURN VALUE

       sasl_server_step  returns  an  integer which corresponds to one of the SASL error 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_errors(3), sasl_server_init(3), sasl_server_new(3), sasl_server_start(3)

SASL
								   10 July 2001 					       sasl_server_step(3)