NULL is defined to be<datatype> *)0 - this means regardless of the underlying architecture
if p == 0 and p is a pointer it is guaranteed to be unassigned. Therefore
evaluate the same. NULL is fairly new. Old C code uses code like (char**)0 all the time. Example - this is in the strtoul definition on the manpage for systems that have C89 compilers.
hi
I wrote the following makefile, I have just one problem, when i type make clean I get the message make 'clean' is up to date and any obj file is removed from my folder, what's wrong?
Thank you
CC = cc
all: es.o elaboration.o
$(CC) -o es es.o elaboration.o
elaboration.o:... (0 Replies)
08-18-2008 11:00 AM
Cluster computing has played a pivotal role in the way research is conducted in educational environments. Because the amount of available money and hardware varies between university researchers, often it's necessary to find a clustering solution that can work well on a small... (0 Replies)
I'm running the following rsync command to sync a directory between the 2 servers:
rsync -az --delete --stats /some_dir/ server_name:/some_dir
I'm getting the following output:
Number of files: 655174
Number of files transferred: 14221
Total file size: 1138531979331 bytes
Total... (0 Replies)
It's been a while since I had to write a Makefile, but I've managed to clobber this together:
SRC=module1.c module2.c
OBJS=$(SRC:%.c=%.o)
HDR=include1.h include2.h
CC=gcc
CFLAGS=-Wall -ggdb -D_XOPEN_SOURCE -I. -ansi
all: program
program: $(OBJS)
$(CC) $(CFLAGS) -o $@ $(OBJS)
... (3 Replies)
Can someone explain the correlation between how sar names the disk drives and how the rest of the OS names the disk drives?
sar lists my disk drives as sd0, sd1, sd2, etc.....
while format lists my disk drives as c1t0d0, c1t1d0, c1t2d0,etc...
And also why sar shows 8 disks but format... (2 Replies)
I stumbled upon this thread and one aspect of it got me thinking. As i am building a small Linux network right now for a friend i would like to hear your opinion on this.
I'd like to respectfully disagree. I think the Linux habit of disabling root login per default is wrong (not entirely... (6 Replies)
I'm trying to send the file list as parameter to another job and execute it.
But the loop doesn't work, the inner job is running only once and not twice as expected
for filelist in $(ls -rt *.txt | tail -2)
do
echo $filelist
export filelist
cmd="$Program -config $configfile -autoexec... (11 Replies)
We have several dozen Redhat 5, 6 and 7 servers that are running Oracle databases. On some databases we are using automatic memory management, which uses shared memory. On other databases we are use manual memory management, which does not use shared memory.
When I see that a server is swapping... (2 Replies)
Discussion started by: gandolf989
2 Replies
LEARN ABOUT MOJAVE
sasl_errstring
sasl_errstring(3) SASL man pages sasl_errstring(3)NAME
sasl_errstring - Translate a SASL return code to a human-readable form
SYNOPSIS
#include <sasl/sasl.h>
const char * sasl_errstring(int saslerr,
const char * langlist,
const char ** outlang);
DESCRIPTION
sasl_usererr is called to convert a SASL return code (an integer) into a human readable string. At this time the only language available is
american english written by programmers (aka gobbledygook). Note that a server should call sasl_usererr on a return code first if the
string is going to be sent to the client.
saslerr specifies the error number to convert.
langlist is currently unused; Use NULL.
outlang specifies the desired RFC 1766 language for output. NULL defaults to "en-us," currently the only supported language.
It should be noted that this function is not the recommended means of extracting error code information from SASL, instead application
should use sasl_errdetail(3), which contains this information (and more)
RETURN VALUE
Returns the string. If langlist is NULL, US-ASCII is used.
CONFORMING TO
RFC 4422
SEE ALSO sasl(3), sasl_errdetail(3), sasl_errors(3)SASL 10 July 2001 sasl_errstring(3)