Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators Stomp has created two threads recently that can't be read Post 303029241 by stomp on Wednesday 23rd of January 2019 03:31:44 PM
Old 01-23-2019
Another idea:

I was promoted by an automatic change last week or so to group "forum advisor". Maybe this is connected to this issue?
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Does WIN2K stomp on the boot record like NT?

My home PC is dual boot with Linux and Win98. I want to upgrade both to a newer version, and have the Linux CD's now. What I need to know is does Win2K Pro stomp (write over LiLo) on the boot record like NT (2 Replies)
Discussion started by: 98_1LE
2 Replies

2. UNIX for Advanced & Expert Users

Threads and Threads Count ?

Hi all, How can I get the list of all Threads and the Total count of threads under a particular process ? Do suggest !! Awaiting for the replies !! Thanks Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies

3. Programming

shared memory read/write using threads

I am looking for C program source code. Could you please help me in finding the source code required mentioned below. program to create multiple threads (one master thread and rest worker threads) and using the threads write into and read from shared memory Restrictions: Only one thread... (2 Replies)
Discussion started by: kumars
2 Replies

4. Shell Programming and Scripting

cron job issue..i hav read the basic threads already...

hi friends well m facing a different sort of issue in my cron. i hav set job like this 30 09 * * 1 /bin/backup14M 01 14 * * 1 /bin/backup14N 20 18 * * 1 /bin/backup14E that is for every Monday at three different times. but, first job executes well, later ones do not. I checked my... (13 Replies)
Discussion started by: oracle.test2
13 Replies

5. Shell Programming and Scripting

[Solved] Find Files Created Recently and Print

Hi, I'm looking to create a script which will find all the files created in the last 24h in a directory starting with a few different letters and send them to the printer. This would be run through the cron each morning to print the last 24 hours files. I have started with this to find all... (2 Replies)
Discussion started by: rab
2 Replies

6. Shell Programming and Scripting

How to read a file name that was recently edited when listed using ls command?

I was trying to write a script that will process recently creatd file. From below, the script should process input_20111230.dat file. sam:/top/work/data/input: ls -ltr input_*.dat -rw-rw-rw- 1 work edprod 455668 Dec 24 09:16 input_20111224.dat -rw-r--r-- 1 work edprod ... (7 Replies)
Discussion started by: siteregsam
7 Replies

7. Forum Support Area for Unregistered Users & Account Problems

Unable to read threads when logged in

I'm getting the following error (or something similar) whenever I try to view a thread when I'm logged in. That is, I login, hit "New Posts", get a list of theads, click on one (in this example is was the "Not allowed to post URLs" thread), then get the following HTML error page instead of the... (1 Reply)
Discussion started by: cnamejj
1 Replies
STDARG(3)						   BSD Library Functions Manual 						 STDARG(3)

NAME
stdarg, va_arg, va_copy, va_end, va_start -- variable argument lists SYNOPSIS
#include <stdarg.h> void va_start(va_list ap, last); type va_arg(va_list ap, type); void va_copy(va_list dest, va_list src); void va_end(va_list ap); DESCRIPTION
A function may be called with a varying number of arguments of varying types. The include file <stdarg.h> declares a type (va_list) and defines three macros for stepping through a list of arguments whose number and types are not known to the called function. The called function must declare an object of type va_list which is used by the macros va_start(), va_arg(), va_end(), and, optionally, va_copy(). The va_start() macro initializes ap for subsequent use by va_arg(), va_copy() and va_end(), and must be called first. The parameter last is the name of the last parameter before the variable argument list, i.e. the last parameter of which the calling function knows the type. Because the address of this parameter is used in the va_start() macro, it should not be declared as a register variable, or as a function or an array type. The va_start() macro returns no value. The va_arg() macro expands to an expression that has the type and value of the next argument in the call. The parameter ap is the va_list ap initialized by va_start(). Each call to va_arg() modifies ap so that the next call returns the next argument. The parameter type is a type name specified so that the type of a pointer to an object that has the specified type can be obtained simply by adding a * to type. If there is no next argument, or if type is not compatible with the type of the actual next argument (as promoted according to the default argument promotions), random errors will occur. If the type in question is one that gets promoted, the promoted type should be used as the argument to va_arg(). The following describes which types are promoted (and to what): - short is promoted to int - float is promoted to double - char is promoted to int The first use of the va_arg() macro after that of the va_start() macro returns the argument after last. Successive invocations return the values of the remaining arguments. The va_copy() macro makes dest a copy of src as if the va_start() macro had been applied to it followed by the same sequence of uses of the va_arg() macro as had previously been used to reach the present state of src. The va_copy() macro returns no value. The va_end() macro handles a normal return from the function whose variable argument list was initialized by va_start() or va_copy(). The va_end() macro returns no value. EXAMPLES
The function foo() takes a string of format characters and prints out the argument associated with each format character based on the type. void foo(char *fmt, ...) { va_list ap; int d, c; char *s; double f; va_start(ap, fmt); while (*fmt) switch (*fmt++) { case 's': /* string */ s = va_arg(ap, char *); printf("string %s ", s); break; case 'd': /* int */ d = va_arg(ap, int); printf("int %d ", d); break; case 'c': /* char */ c = va_arg(ap, int); /* promoted */ printf("char %c ", c); break; case 'f': /* float */ f = va_arg(ap, double); /* promoted */ printf("float %f ", f); } va_end(ap); } COMPATIBILITY
These macros are not compatible with the historic macros they replace. A backward compatible version can be found in the include file <varargs.h>. STANDARDS
The va_start(), va_arg(), va_copy(), and va_end() macros conform to ISO/IEC 9899:1999 (``ISO C99''). HISTORY
The va_start(), va_arg() and va_end() macros were introduced in ANSI X3.159-1989 (``ANSI C89''). The va_copy() macro was introduced in ISO/IEC 9899:1999 (``ISO C99''). BUGS
Unlike the varargs macros, the stdarg macros do not permit programmers to code a function with no fixed arguments. This problem generates work mainly when converting varargs code to stdarg code, but it also creates difficulties for variadic functions that wish to pass all of their arguments on to a function that takes a va_list argument, such as vfprintf(3). BSD
August 18, 2002 BSD
All times are GMT -4. The time now is 11:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy