I want to run my script and want to ensure it captures all logging.
For e.g I got this from another forum
The script will print stderr onto the putty terminal and log all script output into timer_log.log
How can I also print the stdout to the putty terminal too.
I am using a KSH script.
Thanks.
Moderator's Comments:
Please use CODE tags as required by forum rules!
Last edited by RudiC; 03-21-2019 at 05:45 AM..
Reason: Added CODE tags.
I have a SCO R5 Open Server Box running at a remote location, and from time to time it seems to "spontaneously" re-boot itself. Is there a specific log file that I can examine to see why the machine is doing this ? Any suggestions gratefully appreciated (1 Reply)
G'day
Just wondering if anyone out there knows how to log files, using the example I provided in the earlier message / question earlier today:
:confused:
If I was to backup a file, how could I setup a log file to record the filename, date (This one I've got figured), and that the file was... (4 Replies)
Is there a file that captures info whenever someone logs to su? i know it comes across as standard output on the server, but is it saved anywhere? Time and date info included??
thanks, kym (1 Reply)
Hi, just wriiten a sh script and as my script will try to log into another server to delete some files but when i run , it keeps on saying that my files do not exist. It seems to refer to my local directory instead. Below is my script :
FTP_HOST=ip_number
FTP_USER="user password"
... (1 Reply)
Hi all!
On our current Solaris 8 machine we only have "standard" logging configured, and now i need to put on more. What i specificly need is time in the logfiles. Ex. When a user is logging in,
when a user makes it self SU. etc.
Regards...
dOzY (3 Replies)
Discussion started by: dozy
3 Replies
6. Post Here to Contact Site Administrators and Moderators
Hi Everyone. First, I want to thank all of you for letting me participate in this great group.
I am having a bit of a problem.
After I get an email from a responder, I login to make my reply.
In the mean time I get another response by email from another member, I go to reply to them and I... (6 Replies)
Hi
I am new to this Scripting process and would like to know How can i write a ksh script that will call other ksh scripts and write the output to a file and/or email.
For example
-------
Script ABC
-------
a.ksh
b.ksh
c.ksh
I need to call all three scripts execute them and... (2 Replies)
Hi there,
I'm encountering problems on an AIX system when using following in my script.
find . -name *.edi -type f -exec sh -c 'scp {} $user@$server:$path || exit 5; mv {} $sent || exit 7' \;
the error i get is following
find: 0652-018 An expression term lacks a required... (4 Replies)
Good morning all,
I have a ksh script that I would like to log all "Terminal" out to a log file. I have tried several different methods to no avail! Below is my script and any advice or assitance would be great! The script works great but can not figure out how to log all outputs to a log... (4 Replies)
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
LEARN ABOUT DEBIAN
inoticoming
INOTICOMING(1) INOTICOMING INOTICOMING(1)NAME
inoticoming - trigger actions when files hit an incoming directory
SYNOPSIS
inoticoming [ global-options ] directory actions*
DESCRIPTION
Inoticoming is a daemon to watch a directory with Linux's inotify framework and trigger actions once files with specific names are placed
in there.
For example it can be used to wait for .changes files uploaded into a directory and call reprepro to put them into your repository.
GLOBAL OPTIONS --foreground
Do not fork, but stay in the foreground and log to stderr.
--logfile filename
After forking in the background, log to the specified filename instead of syslog.
--pid-file filename
Write the pid of the running instance into filename.
--initialsearch
First search the directory for files already existing and process them with the given rules as if they just appeared. If files show
up in this inital phase, they may be processed twice, but should never be missed. (Unless they are too many and the inotify queue
overflows).
ACTIONS
Each action description is an optional list of options for this action (which files to call it for, what directory to change into before
executing it, ...), followed by the command and its arguments ended with a single ; as argument. Like:
inoticoming --foreground / --regexp ^v echo There appeared {} in the root directory. ; (Note that the before the ; is needed if and only
if you calling it from a shell or anything else interpreting the ; on its own).
ACTION OPTIONS
--prefix string
Only trigger this action, if the filename starts with the specified string.
--suffix string
Only trigger this action, if the filename ends with the specified string.
--regexp regular expression
Only trigger this action, if the filename matches the specified regular expression.
--chdir directory
Change into directory before executing the specified commands. (Note that since it is a well-behaved daemon, its working directory
is / which will be inherited by all actions).
--stdout-to-log
Redirect the command's output (stdout) to the logfile.
--stderr-to-log
Redirect the command's error output (stderr) to the logfile.
EXAMPLES
inoticoming --logfile logs/ilog --pid-file pid $INCOMINGDIR --suffix .changes --stderr-to-log reprepro -s -b $REPREPROBASEDIR --waitforlock
1000 processincoming rulename {} ;
This will call reprepro for every new .changes file. Note that giving {} as argument to processincoming (which inoticoming will
replace with the filename) so that only that .changes file is processed and reprepro will not complain about a possible other yet
incomplete .changes file is only available starting with reprepro version 2.2.2.
PROBLEMS
There is no handling of queue overflows yet.
REPORTING BUGS
Report bugs or wishlist requests to the Debian BTS
(e.g. by using reportbug inoticoming under Debian)
or directly to <brlink@debian.org>.
COPYRIGHT
Copyright (C) 2007 Bernhard R. Link
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
inoticoming 2007-08-18 INOTICOMING(1)