04-01-2008
ls -l | grep -v ".sh"
Note that this will exclude files that have '.sh' ANYWHERE in the file name....
10 More Discussions You Might Find Interesting
1. Linux
Hi all,
I wanted to install the latest version of firefox 2 but it seems when I attempt to install it, it seems to be saying it is looking for c libraries version 2.3? I believe I currently have an older version of the c libraries. I am currently running Sun's JDS Linux 2003. My Mozilla web... (1 Reply)
Discussion started by: scriptingmani
1 Replies
2. Linux
I want to build a load-balancing cluster and I the multiprocess support then I read:
'Any single program that can run as multiple processes can benefit from OpenMosix: "The GIMP" photo editor and the "kandel" fractal generator are known to do this.
Unless I can find a load-balancing cluster... (1 Reply)
Discussion started by: Advice Pro
1 Replies
3. Shell Programming and Scripting
Hi I am going to migrate our datawarehouse system from HP Tru 64 Unix to the Red Hat Linux.
Inside the box, it is running around 40 cron jobs; inside each cron job, it is calling other shell script files, and the shell script files may again call other shell script files or ctl files(for... (1 Reply)
Discussion started by: franksubramania
1 Replies
4. Shell Programming and Scripting
While doing cat on a large file (3 GB file) , I am getting the no space error in the shell script hugefile.sh.
Eg: for i in `cat hugefile.txt`
do
echo "$i"
done
error: hugefile.sh: no space
Please let me know your thoughts in handling this no space issue. (2 Replies)
Discussion started by: techmoris
2 Replies
5. Shell Programming and Scripting
Hi guys. Hopefully this question will make sense!
Continuing on my script to automatically copy some huge files across the network onto various servers as background jobs, I need to be able to check that each job has finished successfully.
The script below shows what I want - almost. The... (2 Replies)
Discussion started by: dlam
2 Replies
6. UNIX for Dummies Questions & Answers
Hello,
The scenario is as follows, I have a background process running initially for which i know the PID on machine1. I use ssh from machine 2 to execute a script in machine 1. For some reason the back ground process is terminated. I would like to know which process caused the ... (1 Reply)
Discussion started by: prasbala
1 Replies
7. Shell Programming and Scripting
Hello,
The scenario is as follows, I have a background process running initially for which i know the PID on machine1. I use ssh from machine 2 to execute a script in machine 1. For some reason the back ground process is terminated. I would like to know which process caused the... (6 Replies)
Discussion started by: prasbala
6 Replies
8. Homework & Coursework Questions
i have to create a simple program for my programming class and mij ide is giving me some errors. The program has to calculate the number of figures entered by a hid ended by a "0"
the code i've written is:
// number of numbers.cpp : Defines the entry point for the console application.
//... (2 Replies)
Discussion started by: metal005
2 Replies
9. Shell Programming and Scripting
I have a script which will run for sometime, i want to monitor it's progress by sending out a mail by runing a infinite loop from command line
for eg. this is the script
$cat script1.sh
#!/usr/bin/ksh
i=0
while
do
sleep 2
echo $i hi
i=`expr $i + 1`
done > testprog.out
... (5 Replies)
Discussion started by: sam05121988
5 Replies
10. UNIX for Beginners Questions & Answers
i use the split command to split a one terabyte backup file into 10 chunks of 100 GB each. The files are split one after the other. While the files is being split, I will like to scp the files one after the other as soon as the previous one completes, from server A to Server B. Then on server B ,... (2 Replies)
Discussion started by: malaika
2 Replies
LEARN ABOUT DEBIAN
inoticoming
INOTICOMING(1) INOTICOMING INOTICOMING(1)
NAME
inoticoming - trigger actions when files hit an incoming directory
SYNOPSIS
inoticoming [ global-options ] directory actions*
DESCRIPTION
Inoticoming is a daemon to watch a directory with Linux's inotify framework and trigger actions once files with specific names are placed
in there.
For example it can be used to wait for .changes files uploaded into a directory and call reprepro to put them into your repository.
GLOBAL OPTIONS
--foreground
Do not fork, but stay in the foreground and log to stderr.
--logfile filename
After forking in the background, log to the specified filename instead of syslog.
--pid-file filename
Write the pid of the running instance into filename.
--initialsearch
First search the directory for files already existing and process them with the given rules as if they just appeared. If files show
up in this inital phase, they may be processed twice, but should never be missed. (Unless they are too many and the inotify queue
overflows).
ACTIONS
Each action description is an optional list of options for this action (which files to call it for, what directory to change into before
executing it, ...), followed by the command and its arguments ended with a single ; as argument. Like:
inoticoming --foreground / --regexp ^v echo There appeared {} in the root directory. ; (Note that the before the ; is needed if and only
if you calling it from a shell or anything else interpreting the ; on its own).
ACTION OPTIONS
--prefix string
Only trigger this action, if the filename starts with the specified string.
--suffix string
Only trigger this action, if the filename ends with the specified string.
--regexp regular expression
Only trigger this action, if the filename matches the specified regular expression.
--chdir directory
Change into directory before executing the specified commands. (Note that since it is a well-behaved daemon, its working directory
is / which will be inherited by all actions).
--stdout-to-log
Redirect the command's output (stdout) to the logfile.
--stderr-to-log
Redirect the command's error output (stderr) to the logfile.
EXAMPLES
inoticoming --logfile logs/ilog --pid-file pid $INCOMINGDIR --suffix .changes --stderr-to-log reprepro -s -b $REPREPROBASEDIR --waitforlock
1000 processincoming rulename {} ;
This will call reprepro for every new .changes file. Note that giving {} as argument to processincoming (which inoticoming will
replace with the filename) so that only that .changes file is processed and reprepro will not complain about a possible other yet
incomplete .changes file is only available starting with reprepro version 2.2.2.
PROBLEMS
There is no handling of queue overflows yet.
REPORTING BUGS
Report bugs or wishlist requests to the Debian BTS
(e.g. by using reportbug inoticoming under Debian)
or directly to <brlink@debian.org>.
COPYRIGHT
Copyright (C) 2007 Bernhard R. Link
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
inoticoming 2007-08-18 INOTICOMING(1)