Sponsored Content
Top Forums Programming [c]Why first file is creating after the second. How to avoid Post 302655593 by ezee on Wednesday 13th of June 2012 11:27:27 AM
Old 06-13-2012
[c]Why first file is creating after the second. How to avoid

Hi,

My Code is as below:
Code:
nbECRITS = fwrite(strstr(data->buffer, ";") + 1, sizeof(char), (data->buffsize) - LEN_NOM_FIC, fic_sortie);
  fclose(fic_sortie);
 
 
 sprintf(PATH_BALISE, "%s.balise", PATH);
fic_balise_data = fopen(PATH_BALISE, "a+");
if (fic_balise_data == NULL) {
fprintf(fic_log, "\nErreur sur l'w mq.exe, au niveau de la creation du fichier balise de sortie \"%s\": ", PATH_BALISE);
fprintf(fic_log, "\ncreation impossible\n");
CR = ERR_FICHIER_BALISE;
break;
}

Here fic_sortie associated file is sometimes created after the file with .balise extension.[x:1000].
What is the bug here in this code.

Thanks for you time and reply...Smilie
 

10 More Discussions You Might Find Interesting

1. Ubuntu

Avoid creating temporary files on editing a file in Ubuntu

Hi, My ubuntu flavor always create temporary files having filename followed by ~ on editing. For eg: if I am editing a file called "sip.c", automatically a temporary (bkup) file is getting created with the name "sip.c~". How to avoid this file creation? (7 Replies)
Discussion started by: royalibrahim
7 Replies

2. UNIX for Dummies Questions & Answers

Avoid Duplicates in a file

Hi Gurus, I had a question regarding avoiding duplicates.i have a file abc.txt abc.txt ------- READER_1_1_1> HIER_28056 XML Reader: Error occurred while parsing:; line number ; column number READER_1_3_1> Sun Mar 23 23:52:48 2008 READER_1_3_1> HIER_28056 XML Reader: Error occurred while... (7 Replies)
Discussion started by: pssandeep
7 Replies

3. Shell Programming and Scripting

How to avoid a temp file

Hi all. I want to check the free space on a given FS and process the output. Right now, I'm using a temp file to avoid using df twice. This is what I'm doing #!/usr/bin/ksh ... df -k $FS_NAME > $TMP_FILE 2>&1 if ]; then RESULT="CRITICAL - $(cat $TMP_FILE)" else cat $TMP_FILE | ...... (3 Replies)
Discussion started by: fox1212
3 Replies

4. HP-UX

Parameter to avoid file being deleted by SAM

Good afternoon. I am a newbie. We just had a potentially big problem (negated to having good backups). Basically, there is an option in SAM, to delete all the data from the system that a user ever created. Lo and behold, silly me, I choose that option, and all sorts of needed files... (5 Replies)
Discussion started by: instant000
5 Replies

5. Shell Programming and Scripting

Avoid file creation in a script...achive same result

Guys following lines help me in getting numbers from PID column ,to be thrown into first column of a CSV file. COLUMNS=2047 /usr/bin/ps -eo pid,ppid,uid,user,args | grep -v "PID" > /tmp/masterPID.txt cat /tmp/masterPID.txt|while read line do PID=`echo $line|awk '{print $1}'` echo "$PID"... (4 Replies)
Discussion started by: ak835
4 Replies

6. Shell Programming and Scripting

avoid open file to check field.

Hi Everyone, # cat a.txt 94,aqqc,62345907, 5,aeec,77, # cat 1.pl #!/usr/bin/perl use strict; use warnings; use Date::Manip; open(my $FA, "/root/a.txt") or die "$!"; while(<$FA>) { chomp; my @tmp=split(/\,/, $_); if (index($tmp, "qq") ne -1) { ... (4 Replies)
Discussion started by: jimmy_y
4 Replies

7. Shell Programming and Scripting

How to avoid Newline character in generated text file?

Hi All, Just need small help in resolving the special new line character in generated output file. In one of my shell script I am using following lines to get the spool file (i.e. sfile.txt) and AAA_XXXX_p111_n222.txt AAA_YYYY_p111_n222.txt Here assuming v_pnum="p111" v_nid="n222" ... (1 Reply)
Discussion started by: shekharjchandra
1 Replies

8. Shell Programming and Scripting

How to avoid Delimiter occuring in column values in .csv file

Hello Gurus, I need to create a file from a .csv file extracting specific columns only. File structure is Column1,Column2,Column3,Column4 abcd,1234,"asdf, tew,123",123456 efgh,234,asdf,654321 My output file should have abcd,123456 efgh,654321 Can you pls help me with the code. ... (10 Replies)
Discussion started by: ritesh.bhawsar
10 Replies

9. Shell Programming and Scripting

Avoid overwriting backup file when multiple entries need to replace in one file input from another

Hello, I have been working on script in which search and replace the multiple pattern. 1. update_params.sh read the multiple pattern from input file ParamMapping.txt(old_entry|New_entry) and passing this values one by one to change_text.sh 2. change_text.sh read... (0 Replies)
Discussion started by: ketanraut
0 Replies

10. Shell Programming and Scripting

Write only changes to file - avoid duplicates

I want to create a file, to save a list of fail2ban blocked ip addresses. So I thought I'd create a loop that will check with fail2ban every minute, and write the ip addresses to a file. while true; do echo $(fail2ban-client status asterisk-iptables | grep 'IP list' | sed 's/.*://g' | sed -e... (4 Replies)
Discussion started by: aristosv
4 Replies
explain_fwrite(3)					     Library Functions Manual						 explain_fwrite(3)

NAME
explain_fwrite - explain fwrite(3) errors SYNOPSIS
#include <libexplain/fwrite.h> const char *explain_fwrite(const void *ptr, size_t size, size_t nmemb, FILE *fp); const char *explain_errno_fwrite(int errnum, const void *ptr, size_t size, size_t nmemb, FILE *fp); void explain_message_fwrite(char *message, int message_size, const void *ptr, size_t size, size_t nmemb, FILE *fp); void explain_message_errno_fwrite(char *message, int message_size, int errnum, const void *ptr, size_t size, size_t nmemb, FILE *fp); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the fwrite(3) system call. explain_fwrite const char *explain_fwrite(const void *ptr, size_t size, size_t nmemb, FILE *fp); The explain_fwrite function is used to obtain an explanation of an error returned by the fwrite(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (fwrite(ptr, size, nmemb, fp) < 0) { fprintf(stderr, "%s ", explain_fwrite(ptr, size, nmemb, fp)); exit(EXIT_FAILURE); } ptr The original ptr, exactly as passed to the fwrite(3) system call. size The original size, exactly as passed to the fwrite(3) system call. nmemb The original nmemb, exactly as passed to the fwrite(3) system call. fp The original fp, exactly as passed to the fwrite(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_errno_fwrite const char *explain_errno_fwrite(int errnum, const void *ptr, size_t size, size_t nmemb, FILE *fp); The explain_errno_fwrite function is used to obtain an explanation of an error returned by the fwrite(3) system call. The least the mes- sage will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (fwrite(ptr, size, nmemb, fp) < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_fwrite(err, ptr, size, nmemb, fp)); exit(EXIT_FAILURE); } errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. ptr The original ptr, exactly as passed to the fwrite(3) system call. size The original size, exactly as passed to the fwrite(3) system call. nmemb The original nmemb, exactly as passed to the fwrite(3) system call. fp The original fp, exactly as passed to the fwrite(3) system call. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. explain_message_fwrite void explain_message_fwrite(char *message, int message_size, const void *ptr, size_t size, size_t nmemb, FILE *fp); The explain_message_fwrite function may be used to obtain an explanation of an error returned by the fwrite(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. This function is intended to be used in a fashion similar to the following example: if (fwrite(ptr, size, nmemb, fp) < 0) { char message[3000]; explain_message_fwrite(message, sizeof(message), ptr, size, nmemb, fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. ptr The original ptr, exactly as passed to the fwrite(3) system call. size The original size, exactly as passed to the fwrite(3) system call. nmemb The original nmemb, exactly as passed to the fwrite(3) system call. fp The original fp, exactly as passed to the fwrite(3) system call. explain_message_errno_fwrite void explain_message_errno_fwrite(char *message, int message_size, int errnum, const void *ptr, size_t size, size_t nmemb, FILE *fp); The explain_message_errno_fwrite function may be used to obtain an explanation of an error returned by the fwrite(3) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail. This function is intended to be used in a fashion similar to the following example: if (fwrite(ptr, size, nmemb, fp) < 0) { int err = errno; char message[3000]; explain_message_errno_fwrite(message, sizeof(message), err, ptr, size, nmemb, fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. ptr The original ptr, exactly as passed to the fwrite(3) system call. size The original size, exactly as passed to the fwrite(3) system call. nmemb The original nmemb, exactly as passed to the fwrite(3) system call. fp The original fp, exactly as passed to the fwrite(3) system call. SEE ALSO
fwrite(3) binary stream output explain_fwrite_or_die(3) binary stream output and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller explain_fwrite(3)
All times are GMT -4. The time now is 03:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy