OS: RedHat
Shell: bash
User: root
no chrooted environment, no special non-printing characters.
First observation: the paths in the script are not absolute paths. This might lead to no directories/files being found when the script is executed in a wrong current path. Change these paths to absolute paths to make the script more robust.
Here is another take at problem determination: modify your script by switching on printing of the interpreted lines:
Now start the script this way:
and post the contents of the file myscript.log here. I would really be interested in what the problem is here and what the final solution will be.
linux redhat 8.0
I am getting accustomed to using the -exec command to get around my databse.. and use it to edit and update files..! is this more apllicable than jumping from one directory to the other.. I have set up the databse so that the inode #'s are accessable and can get me from one... (0 Replies)
hai
i want know the difference between two shell scripts those are
1)
a=2004
echo $a #output------2004
exec < inputfile
while read line
do
echo $a #output-------2004
a=2005
echo $line
echo $a ... (1 Reply)
All,
I am using below shell script to output the content to outputfile.txt. What I am looking for is in addition to outputfile.txt, I want the output to be on standard output too.
exec > outputfile.txt
echo "Starting "
echo "ending" (5 Replies)
How can I use the exec command to log my korn shell session to the screen and the log file?
Currently I have this command:
$exec 1> ${LOG} 2>&1
This logs the output to the log file only. I want it to go to the screen also. Is this possible with this command?
thanks. (10 Replies)
Hi can some one explain the following command , It would really help if some can really elloborate on what is happening out here
export PATH | exec /bin/sh ./auto_approve :q
P.S: This is the first time i am using exec ,so an elloboration what does it do and what is the use of the :q will be... (1 Reply)
Hi,
I have the following lines in a script :
.
.
exec < some_file
.
.
.
I have very little idea about exec command. I would like to know what this does and what will happen if the file some_file does not exist. Specifically, I would like to know whether the lines following this... (5 Replies)
I have the following bash script lines in a file named test.sh.
#!/bin/bash
#
# Write Date to cron.log
#
echo "Begin SSI Load $(date +%d%b%y_%T)"
#
# Get the latest rates file for processing.
#
d=$(ls -tr /rms/data/ssi | grep -v "processed" | tail -n 1)
filename=$d
export filename... (3 Replies)
Hi all,
Forgive me for asking for help with my first post, but I am struggling here. I've been asked to translate a bash script into a Windows script (probably batch or powershell, not sure yet), so the first step is obviously understand what the bash script is doing. But I have no experience in... (5 Replies)
Hello.
From a script, a command for a test is use :
find /home/user_install -maxdepth 1 -type f -newer /tmp/000_skel_file_deb ! -newer /tmp/000_skel_file_end -name '.bashrc' -o -name '.profile' -o -name '.gtkrc-2.0' -o -name '.i18n' -o -name '.inputrc'
Tha command... (3 Replies)
Discussion started by: jcdole
3 Replies
LEARN ABOUT DEBIAN
ohcount
OHCOUNT(1) User Commands OHCOUNT(1)NAME
ohcount - manual page for ohcount 3.0.0
SYNOPSIS
ohcount [option] [paths...]
DESCRIPTION
Ohloh source code line counter command line tool.
http://www.ohloh.net/
[option] can be one of the following:
-a, --annotate
-d, --detect
-h, --help
-i, --individual
-l, --license
-re
-s, --summary
-a, --annotate Show annotated source code
The contents of all source code files found within the given paths will be emitted to stdout. Each line will be prefixed with a
tab-delimited language name and semantic categorization (code, comment, or blank).
-d, --detect Find source code files
Recursively find all source code files within the given paths. For each source code file found, the file name will be emitted to
stdout prefixed with a tab-delimited language name.
-h, --help Display this message
-i, --individual Count lines of code per file
Count lines in all source code files within the given paths, and emit a report of the lines of code, comments, and blanks in each
language per file.
-l, --license
Displays detected licensing information contained in each source code file.
-re
Prints raw entity information to the screen (mainly for debugging).
-s, --summary Count lines of code (default)
Count lines in all source code files within the given paths, and emit a report of the total number of lines of code, comments, and
blanks in each language. This is the default action.
[paths] can refer to any number of individual files or directories.
Directories will be probed recursively. If no path is given, the current directory will be used.
ohcount 3.0.0 September 2011 OHCOUNT(1)