I was able to get ouput on console and log file, however the output in log file is not being updated but re-written. Guess we need to have >> at step to append output to be written in log file every time the script runs. Below is the updated script now.
Hi,
How can i redirect the traces to both the console and to a file..
The way i was doing was:
/home/harika/harika/samp.exe
if ; then
echo "executed the first exe.." >> /dev/console;/home/harika/harika/trace.txt
/home/harika/harika/memset.exe
echo "executed the... (1 Reply)
Hi all,
I have a requirement, where I need to do some calculations and based on the results I need to write a message to the user from a shell script.
Is it possible to `write' inside the script? Something like the below one..
#! /bin/ksh
write user12 << EOF
Hello World
<<EOF
For... (2 Replies)
Hi Dudes,
Can you please suggest me how to create a logfile to track the below script output ? Thanks
#!/bin/ksh
# backup the "std" I/P file descriptor
exec 5<&0
#echo "Proceed ?"
while read config_line; do
# backup the I/P file descriptor of "while" block
exec 6<&0
# restore the... (2 Replies)
Hey everyone
I have a sparc enterprise T2000 I'm trying to install solaris 10 on. The only way I can connect to it is the SER MGT console, but I'm not getting anything to display (in Hyper terminal, or PUTTY) when I boot it. Upon googleing, all I get back is "No output may have been generated.... (4 Replies)
I created a script to do some work. I want to use "echo" to redirect "date" to log file. echo works to screen. But cannot redirect first or second "echo" output to logfile. Please help. My code looks like:
STARTTIME=`date +%m-%d-%Y`
LOGFILE=/directory/logfile.log
echo "Start time:" $STARTTIME... (8 Replies)
Hello,
As stated in the title, I do some hacked parallel processing by running multiple instances of bash scripts, each in their own subshell. The code looks like this,
# launch one batch-train script in background for each value in fold group list
for FOLD_GROUP in "${FOLD_GROUP_LIST}"
do
... (5 Replies)
Bonjour,
I've wrote a script to monitor a logfile in realtime. It is working almost perfeclty except for two things.
The script use the following technique :
tail -fn0 $logfile | \
while read line ; do
... some stuff
done
First one, I'd like a way to end the monitoring script if a... (3 Replies)
Friends,
I pass some runtime arguments (date, number) through ksh script to Oracle procedure, use input value and pass it on to procedure.
Oracle procedure gets input value, run query and logs everything in the logfile.
I'm facing with couple of challenges
1. Even though I pass all... (5 Replies)
Discussion started by: homer4all
5 Replies
LEARN ABOUT DEBIAN
bootlogd
BOOTLOGD(8) Linux System Administrator's Manual BOOTLOGD(8)NAME
bootlogd - record boot messages
SYNOPSIS
/sbin/bootlogd [-c] [-d] [-r] [-s] [-v] [ -l logfile ] [ -p pidfile ]
DESCRIPTION
Bootlogd runs in the background and copies all strings sent to the /dev/console device to a logfile. If the logfile is not accessible, the
messages will be kept in memory until it is.
OPTIONS -d Do not fork and run in the background.
-c Attempt to write to the logfile even if it does not yet exist. Without this option, bootlogd will wait for the logfile to appear
before attempting to write to it. This behavior prevents bootlogd from creating logfiles under mount points.
-r If there is an existing logfile called logfile rename it to logfile~ unless logfile~ already exists.
-s Ensure that the data is written to the file after each line by calling fdatasync(3). This will slow down a fsck(8) process running
in parallel.
-v Show version.
-l logfile
Log to this logfile. The default is /var/log/boot.
-p pidfile
Put process-id in this file. The default is no pidfile.
BUGS
Bootlogd works by redirecting the console output from the console device. (Consequently bootlogd requires PTY support in the kernel con-
figuration.) It copies that output to the real console device and to a log file. There is no standard way of ascertaining the real con-
sole device if you have a new-style /dev/console device (major 5, minor 1) so bootlogd parses the kernel command line looking for con-
sole=... lines and deduces the real console device from that. If that syntax is ever changed by the kernel, or a console type is used that
bootlogd does not know about then bootlogd will not work.
AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
SEE ALSO dmesg(8),fdatasync(3).
Jul 21, 2003 BOOTLOGD(8)