I'm having a strange problem with basic
output redirection to a simple log file in csh. When I run this particular output redirection on the command line, it works, but then when I run the same output redirection command
in my c shell script, I get a blank log file. Nothing is output to the screen, either.
It gets even stranger because the
output redirection works within my c shell script on Redhat Linux but not when I run my c shell script on my current operating system, CentOS V. 2.16.0 release 5.8.
Is there some system variable that needs to be set in CentOS V. 2.16.0 release 5.8, or why does
work in *every other situation* (both command line and running in my c shell script on some computers) except when running my csh script on CentOS V. 2.16.0 release 5.8? It should work the same within the cshell script on all computers, shouldn't it? And does anyone have a work-around that will successfully output to a log file in a csh script on CentOS V. 2.16.0 release 5.8?
EDIT: I was thinking maybe some system variable in CentOS V. 2.16.0 release 5.8 is buffering output from csh? I have no idea, though.
Man pages....look at the man pages. If you don't have them, you can find them on-line. Read them when you have nothing better to do. Find new commands and new ways of doing things.
The answer:
The only way to direct the standard output and standard
error separately is by invoking... (0 Replies)
Hi everyone,
Simple scripting question here. I have:
#!/bin/csh
if ( -e $HOME/*.core) then
rm -f $HOME/*.core >& /dev/null
else
echo "No core files to delete."
endif
But I keep getting the /home/user/*.core: no match
dialog. How can I suppress this? or, why is... (0 Replies)
Here is my script
#!/bin/bash
pwd
cd /var/lib/pgsql
Both "pwd" and "cd" are not executed is there any other way i can change the current working directory to /var/lib/pgsql pls help! (9 Replies)
Portion of my script below :
if ; then
NUMBEROFFEILDS=`cat ${BASE_SCRIPT_LOC}/standardfilecleanup.lst|grep -w ${db_file_path}|awk -F: '{print NF}'`
COUNT=4
while ; do
awk_var="$"`echo $COUNT`
file_name1=`cat ${BASE_SCRIPT_LOC}/standardfilecleanup.lst|grep -w... (1 Reply)
I am using perl to perform a search and replace. It works at the command line, but not in the csh shell script
perl -pi -e 's@/Pattern@@g' $path/$file
I used the @ as my delimiter because the pattern contains "/" (3 Replies)
I have a csh script which I am using to run a program
set data = $argv
set inmod = $argv
set nxz = $argv
# Remove the file extension .pmod
set data = ` echo $data | awk 'BEGIN { FS=".dat" } { print $1 }' `
set inmod = ` echo $inmod | awk 'BEGIN { FS=".vmod" } { print... (8 Replies)
I need to count the number of lines in a .txt file and put it in a variable.
I am using the following code
#!/bin/bash
count = $(wc -l "some file.txt" | awk '{print$1}')
echo $count
It is giving the following error.
line3: count: command not foundWhat am I doing wrong here? :confused: (7 Replies)
I have a simple script which will send a curl request and redirect the output to a log file.
for i in {1..20}
do
curl google.com -is >>log.log &
echo "request # $i" >> log.log
doneAfter it completes the execution, if I run the following command I should see 20 lines because I am printing... (4 Replies)
i have strange behavior i have csh file that run java process something like this :
run_server.csh
#!/usr/bin/tcsh
java -Dtest=testparam -cp ${TEST}/lib/device.jar:${TEST}/conf:${TEST}/lib/commons-logging-1.1.1.jar com.device.server
when i run it like this :... (7 Replies)
Discussion started by: umen
7 Replies
LEARN ABOUT MOJAVE
script
SCRIPT(1) BSD General Commands Manual SCRIPT(1)NAME
script -- make typescript of terminal session
SYNOPSIS
script [-adkpqr] [-F pipe] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an
interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).
If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command is given, script will run the specified command with an optional argument vector instead of an interactive shell.
The following options are available:
-a Append the output to file or typescript, retaining the prior contents.
-d When playing back a session with the -p flag, do not sleep between records when playing back a timestamped session.
-F pipe
Immediately flush output after each write. This will allow a user to create a named pipe using mkfifo(1) and another user may watch
the live session using a utility like cat(1).
-k Log keys sent to the program as well as output.
-p Play back a session recorded with the -r flag in real time.
-q Run in quiet mode, omit the start, stop and command status messages.
-r Record a session with input, output, and timestamping.
-t time
Specify the interval at which the script output file will be flushed to disk, in seconds. A value of 0 causes script to flush after
every character I/O event. The default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-D (if
ignoreeof is not set) for the C-shell, csh(1)).
Certain interactive commands, such as vi(1), create garbage in the typescript file. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
ENVIRONMENT
The following environment variables are utilized by script:
SCRIPT
The SCRIPT environment variable is added to the sub-shell. If SCRIPT already existed in the users environment, its value is overwrit-
ten within the sub-shell. The value of SCRIPT is the name of the typescript file.
SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most
shells set this variable automatically).
SEE ALSO csh(1)HISTORY
The script command appeared in 3.0BSD.
The -d, -p and -r options first appeared in NetBSD 2.0 and were ported to FreeBSD 9.2.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when the terminal is in a raw mode where the program being run is doing manual echo.
If script reads zero bytes from the terminal, it switches to a mode when it only attempts to read once a second until there is data to read.
This prevents script from spinning on zero-byte reads, but might cause a 1-second delay in processing of user input.
BSD December 4, 2013 BSD