04-15-2005
csh stderr redirection
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 the stderr
redirect not working? Thanks in advance.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: thehoghunter
0 Replies
2. UNIX for Dummies Questions & Answers
Does anyone know away of redirecting the stderr for a bourne or korn shell script to a file. (5 Replies)
Discussion started by: blakmk
5 Replies
3. Shell Programming and Scripting
Hello all
im trying to use top program in my csh shell
like this :
set topResult = `top | grep server.exe`
but im facing 2 problems
1.when the top program dont installed in the machine im getting error
so can i check in csh if application im using exist
2 the top program gives... (2 Replies)
Discussion started by: umen
2 Replies
4. Shell Programming and Scripting
I have an extraordinary problem with a csh script.....(feel free to berate the use of this but I'm modifying an existing bunch of them)
Anyway, I have a master csh script which in turn calls a second csh script. This second csh script is below. Within this second script are two compiled C++... (1 Reply)
Discussion started by: pollsizer
1 Replies
5. Shell Programming and Scripting
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)
Discussion started by: kristinu
8 Replies
6. Shell Programming and Scripting
I am trying to use one global declaration --> "exec 2>$ERR" to capture all stderr outputs that may occur anywhere in my script.
Then close it at the end of the script using --> "exec 2<&-"
I am using KSH on Solaris 8.
KSH Version M-11/16/88i
If I comment two "exec .." statements in the... (11 Replies)
Discussion started by: kchinnam
11 Replies
7. Shell Programming and Scripting
Hello all,
I have a for loop executing in a script that I want to redirect STDOUT to screen and to file, while directing STDERR to the bit bucket. Here is the general sentax of what I'm doing:
for i in thingy
do
some_command ${i}
done 1>&1 | tee ${LOGFILE} 2> /dev/null
What I am... (2 Replies)
Discussion started by: LinuxRacr
2 Replies
8. Shell Programming and Scripting
Hi all,
can someone help me with the next redirection?
i want to redirect the stdout+stderr of a command to the same file (this i can do by prog &> file)
but in addition i want to redirect only the stderr to a different file.
how can i do this please? (in BASH)
thanks. (4 Replies)
Discussion started by: eee
4 Replies
9. Shell Programming and Scripting
I am running tcsh/csh shell on my machine. lately i have realized my stderr file redirection is not working.
Please find the terminal logs as below:
>echo b c >>& log
>cat log
b c
>echo $a b c >>& log
a: Undefined variable.
>cat log
b c
I have never faced such issues, hence not sure... (5 Replies)
Discussion started by: animesharma
5 Replies
10. Shell Programming and Scripting
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... (5 Replies)
Discussion started by: silencio
5 Replies
CORE(5) BSD File Formats Manual CORE(5)
NAME
core -- memory image file format
SYNOPSIS
#include <sys/param.h>
DESCRIPTION
A small number of signals which cause abnormal termination of a process also cause a record of the process's in-core state to be written to
disk for later examination by one of the available debuggers. (See sigaction(2).) This memory image is written to a file named by default
core.pid, where pid is the process ID of the process, in the /cores directory, provided the terminated process had write permission in the
directory, and the directory existed.
The maximum size of a core file is limited by setrlimit(2). Files which would be larger than the limit are not created.
The core file consists of the Mach-O(5) header as described in the <mach-o/loader.h> file. The remainder of the core file consists of vari-
ous sections described in the Mach-O(5) header.
NOTE
Core dumps are disabled by default under Darwin/Mac OS X. To re-enable core dumps, a privileged user must do one of the following
* Edit /etc/launchd.conf or $HOME/.launchd.conf and add a line specifying the limit limit core unlimited
* A privileged user can also enable cores with launchctl limit core unlimited
* A privileged user can also enable core files by using ulimit(1) or limit(1) depending upon the shell.
SEE ALSO
gdb(1), setrlimit(2), sigaction(2), Mach-O(5), launchd.conf(5), launchd.plist(5), sysctl(8)
HISTORY
A core file format appeared in Version 6 AT&T UNIX.
BSD
June 26, 2008 BSD