Sponsored Content
Top Forums Shell Programming and Scripting How to Append the output of a script running in remote server to a file in local server? Post 302914814 by RudiC on Thursday 28th of August 2014 05:39:55 AM
Old 08-28-2014
Redirect stderr to another text file to capture the err msg. If you need the server as well, you have to take care of that in your script, e.g. echo the server name to stderr if an exit code is not zero.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Transfer file from local unix server to remote server

want to remove the thread thanks (2 Replies)
Discussion started by: indira
2 Replies

2. Shell Programming and Scripting

Transfer file from local unix server to remote server

want to remove this thread. thanks (2 Replies)
Discussion started by: indira
2 Replies

3. Shell Programming and Scripting

Can a script runned in local server access remote server?

Hi, Im creating a script that is supposed to run commands on remote server using sftp. My script is as below: #!/bin/ksh sftp remote_server mypassword cd /u08/mydir/allfiles mget * .. But this is what I got when I runned the script: Connecting to remote server...... (3 Replies)
Discussion started by: luna_soleil
3 Replies

4. Shell Programming and Scripting

How to stop a script running in remote server from local script

Hi, I have googled for quite some time and couldn't able to get what exactly I am looking for.. My query is "how to stop a shell script which is running inside a remote server, using a script"??? can any one give some suggestions to sort this out. (1 Reply)
Discussion started by: mannepalli
1 Replies

5. Shell Programming and Scripting

rsh help - getting the output of remote script to local server.

Hi, I have a script that runs for an hour. Have to run it on remote server and need the output it produces on the remote server to decide for failure or success. I run it through a Autosys Job which logs the outputs, both 1 & 2. I use the commands 1) rsh <SERVER> 'nohup /tmp/xyz.ksh &' 2)... (5 Replies)
Discussion started by: aster007
5 Replies

6. Shell Programming and Scripting

check web server running on local and on remote machine

Hi , How to check whether web server is running from remote machine How to check whether web server is running on web server itself Can any one help me soon (1 Reply)
Discussion started by: satheeshkr_cse
1 Replies

7. Shell Programming and Scripting

preserving the timestamp of a file when copied from remote server to local server using ftp

Hi, I need to copy few files from remote server to local server. I write a shell script to connect to the remote server using ftp and go to that path. Now i need to copy those files in the remote directory to my local server with the timestamp of all those files shouldnt be changed. ... (5 Replies)
Discussion started by: arunkumarmc
5 Replies

8. Shell Programming and Scripting

How to create a file in remote server from local server?

hi, can anyone tell me how can i store the names of a file that are in remote server to a file and then get the file that contains the name in local server? there is a remote server where 5 files are present , say a.txt b.txt c.txt d.txt e.txt i want to write a script in my local... (4 Replies)
Discussion started by: Little
4 Replies

9. Solaris

Script to get files from remote server to local server through sftp without prompting for password

Hi, I am trying to automate the process of fetching files from remote server to local server through sftp. I have the username and password for the remote solaris server. But I need to give password manually everytime i run the script. Can anyone help me in automating the script such that it... (3 Replies)
Discussion started by: ssk250
3 Replies

10. Shell Programming and Scripting

Grep remote multiple hosts output to local server

Hello all, i'm trying to create a report by greping a pattern on multiple remote hosts and creta a simple report, actually i did this, is ther any better way to do this. #!/bin/bash for host in `cat RemoteHosts` do ssh $host -C 'hostname 2>&1; grep ERROR /var/log/WebServer.log.2019-09-21... (0 Replies)
Discussion started by: charli1
0 Replies
explain_fclose(3)					     Library Functions Manual						 explain_fclose(3)

NAME
explain_fclose - explain fclose(3) errors SYNOPSIS
#include <libexplain/fclose.h> const char *explain_fclose(FILE *fp); const char *explain_errno_fclose(int errnum, FILE *fp); void explain_message_fclose(char *message, int message_size, FILE *fp); void explain_message_errno_fclose(char *message, int message_size, int errnum, FILE *fp); DESCRIPTION
These functions may be used to obtain explanations of fclose(3) errors. explain_fclose const char *explain_fclose(FILE * fp); The explain_fclose function is used to obtain an explanation of an error returned by the fclose(3) function. 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 (fclose(fp)) { fprintf(stderr, "%s ", explain_fclose(fp)); exit(EXIT_FAILURE); } fp The original fp, exactly as passed to the fclose(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. Note: This function may be of little diagnostic value, because libc may have destroyed any useful context, leaving nothing for libexplain to work with (this is true of glibc in particular). For files that are open for writing, you will obtain more useful information by first calling fflush(3), as in the following example if (fflush(fp)) { fprintf(stderr, "%s ", explain_fflush(fp)); exit(EXIT_FAILURE); } if (fclose(fp)) { fprintf(stderr, "%s ", explain_fclose(fp)); exit(EXIT_FAILURE); } explain_errno_fclose const char *explain_errno_fclose(int errnum, FILE * fp); The explain_errno_fclose function is used to obtain an explanation of an error returned by the fclose(3) function. 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 (fclose(fp)) { int err = errno; fprintf(stderr, "%s ", explain_errno_fclose(err, 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. fp The original fp, exactly as passed to the fclose(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. Note: This function may be of little diagnostic value, because libc may have destroyed any useful context, leaving nothing for libexplain to work with (this is true of glibc in particular). For files that are open for writing, you will obtain more useful information by first calling fflush(3), as in the following example if (fflush(fp)) { int err = errno; fprintf(stderr, "%s ", explain_errno_fflush(err, fp)); exit(EXIT_FAILURE); } if (fclose(fp)) { int err = errno; fprintf(stderr, "%s ", explain_errno_fclose(err, fp)); exit(EXIT_FAILURE); } explain_message_fclose void explain_message_fclose(char *message, int message_size, FILE *fp); The explain_message_fclose function is used to obtain an explanation of an error returned by the fclose(3) function. 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 (fclose(fp)) { char message[3000]; explain_message_fclose(message, sizeof(message), fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. Because a message return buffer has been supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. fp The original fp, exactly as passed to the fclose(3) system call. Note: This function may be of little diagnostic value, because libc may have destroyed any useful context, leaving nothing for libexplain to work with (this is true of glibc in particular). For files that are open for writing, you will obtain more useful information by first calling fflush(3), as in the following example if (fflush(fp)) { char message[3000]; explain_message_fflush(message, sizeof(message), fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } if (fclose(fp)) { char message[3000]; explain_message_fclose(message, sizeof(message), fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } explain_message_errno_fclose void explain_message_errno_fclose(char *message, int message_size, int errnum, FILE *fp); The explain_message_errno_fclose function is used to obtain an explanation of an error returned by the fclose(3) function. 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 exameple: if (fclose(fp)) { int err = errno; char message[3000]; explain_message_errno_fclose(message, sizeof(message), err, fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } message The location in which to store the returned message. Because a message return buffer has been 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. fp The original fp, exactly as passed to the fclose(3) system call. Note: This function may be of little diagnostic value, because libc may have destroyed any useful context, leaving nothing for libexplain to work with (this is true of glibc in particular). For files that are open for writing, you will obtain more useful information by first calling fflush(3), as in the following example if (fflush(fp)) { int err = errno; char message[3000]; explain_message_errno_fflush(message, sizeof(message), err, fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } if (fclose(fp)) { int err = errno; char message[3000]; explain_message_errno_fclose(message, sizeof(message), err, fp); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } COPYRIGHT
libexplain version 0.52 Copyright (C) 2008 Peter Miller AUTHOR
Written by Peter Miller <pmiller@opensource.org.au> explain_fclose(3)
All times are GMT -4. The time now is 05:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy