Don't know if I understand your question correct, but this works I think:
If no error, result is only in file "errs", if error result is both on screen and in file "errs".
In bash, I need to send the STDOUT and STDERR from a command to one file, and then just STDERR to another file. Doing one or the other using redirects is easy, but trying to do both at once is a bit tricky. Anyone have any ideas? (9 Replies)
Friends
I have to redirect STDERR messages both to screen and also capture the same in a file.
2 > &1 | tee file works but it also displays the non error messages to file, while i only need error messages.
Can anyone help?? (10 Replies)
Hi friends
I am facing one problem while redirecting the out of the stderr and stdout to a file
let example my problem with a simple example
I have a file (say test.sh)in which i run 2 command in the background
ps -ef &
ls &
and now i am run this file and redirect the output to a file... (8 Replies)
working on a c sell script
I think I understand the concept of it, which is:
filename >> file.txt (to appaend)
or filename | tee -a file.txt (to append)
The problem is that my shell script is used with several parameters, and these commands don't seem to work with just filename. They... (2 Replies)
Hi
I am not if this is possible: is it possible in bach (or another shell) to redirect GLOBALLY the stdout/stderr channels to a file.
So, if I have a script
script.sh
cmd1
cmd2
cmd3
I want all stdout/stderr goes to a file. I know I can do:
./script.sh 1>file 2>&1
OR
... (2 Replies)
Hi,
I already searched through the forum and tried to find a answer for my problem but I didn't found a full working solution, thats way I start this new thread and hope, some can help out.
I wonder that I'm not able to find a working solution for the following scenario:
Working in bash I... (8 Replies)
I originally wrote my script using the korn shell and had to port it to bash on a another server. My script is working find for backing up but noticed that now after the move, I am not getting any output to my log files.
Using Korn shell, this worked for me for some odd reason. This was sending... (2 Replies)
Dear all,
redirecting STDOUT & STDERR to file is quite simple, I'm currently using:
exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.logBut during script execution I would like the output come back again to screen, how to do that?
Thanks
Lucas (4 Replies)
Hi folks
I need/want to redirect output (stdout, stderr) from an exec call to separate files. One for stderr only and two(!) different (!) ones for the combined output of stderr and stdout.
After some research and testing i got this so far :
(( exec ${command} ${command_parameters} 3>&1... (6 Replies)
Dear all,
redirecting STDOUT & STDERR to file is quite simple, I'm currently using:
Code:
exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.log
But during script execution I would like the output come back again to screen, how to do that?
Thanks
Luc
edit by bakunin: please use CODE-tags like the... (6 Replies)
Discussion started by: tmonk1
6 Replies
LEARN ABOUT NETBSD
ratecheck
RATECHECK(9) BSD Kernel Developer's Manual RATECHECK(9)NAME
ratecheck -- function to help implement rate-limited actions
SYNOPSIS
#include <sys/time.h>
int
ratecheck(struct timeval *lasttime, const struct timeval *mininterval);
DESCRIPTION
The ratecheck() function provides a simple time interval check which can be used when implementing time-based rate-limited actions. If the
difference between the current monotonically-increasing system time (mono_time) and lasttime is less than the value given by the mininterval
argument, zero is returned. Otherwise, lasttime is set to the current time and a non-zero value is returned.
The motivation for implementing ratecheck() was to provide a mechanism that could be used to add rate limiting to diagnostic message output.
If printed too often, diagnostic messages can keep the system from doing useful work. If the repeated messages can be caused by deliberate
user action or network events, they can be exploited to cause denial of system service.
Note that using a very short time interval (less than a second) for mininterval defeats the purpose of this function. (It doesn't take much
to flood a 9600 baud serial console with output, for instance.)
EXAMPLES
Here is a simple example of use of the ratecheck() function:
/*
* The following variables could be global, in a device softc, etc.,
* depending on the exact usage.
*/
struct timeval drv_lasterr1time; /* time of last err1 message */
long drv_err1count; /* # of err1 errs since last msg */
struct timeval drv_lasterr2time; /* time of last err2 message */
long drv_err2count; /* # of err2 errs since last msg */
/*
* The following variable will often be global or shared by all
* instances of a driver. It should be initialized, so it can be
* patched. Allowing it to be set via an option might be nice,
* but could lead to an insane proliferation of options.
*/
struct timeval drv_errintvl = { 5, 0 }; /* 5 seconds */
/* error handling/reporting function */
void
drv_errhandler(int err1, int err2)
{
/*
* Note that you should NOT use the same last-event
* time variable for dissimilar messages!
*/
if (err1) {
/* handle err1 condition */
...
drv_err1count++;
if (ratecheck(&drv_lasterr1notice,
&drv_errinterval)) {
printf("drv: %ld err1 errors occurred",
drv_err1count);
drv_err1count = 0;
}
}
if (err2) {
/* handle err2 condition */
...
drv_err2count++;
if (ratecheck(&drv_lasterr2notice,
&drv_errinterval)) {
printf("drv: %ld err2 errors occurred",
drv_err2count);
drv_err2count = 0;
}
}
}
SEE ALSO log(9), ppsratecheck(9), printf(9), time_second(9)HISTORY
The ratecheck() function appeared in NetBSD 1.5.
BUGS
ratecheck() may not work as expected, if mininterval is less than the hardware clock interrupt interval (1/hz).
BSD February 2, 2000 BSD