01-13-2012
Viewing changes in directory
Hi,
I have a directory, and there is a job running and constantly writes and removes files from and to this directory.
I would like to see somehow these changes without pressing `ls` every second. Kind of `tail -f` command, but for a directory list and not for file content.
I thought maybe kind of cron job could be useful, but from what I saw in web, the lowest frequency is minutes and not seconds, and it's too slow.
Thanks for the help
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I view files in a directory? (1 Reply)
Discussion started by: Ania
1 Replies
2. UNIX for Dummies Questions & Answers
I have completely blanked out on this and I have done it a million times. I need to modify some tables in unix. What is the command for opening/viewing the tables?
Thanks so much. :o (2 Replies)
Discussion started by: itldp
2 Replies
3. UNIX for Dummies Questions & Answers
How do I view pdf files on a Solaris 9 environment?
Links and such would be grateful.
"AAAAHHH!! They're everywhere!!!" - Halo Grunt (3 Replies)
Discussion started by: antalexi
3 Replies
4. UNIX for Dummies Questions & Answers
I have a file (called CORE) that is a dump created by a crashing process. This file, I believe, is in "binary" form, so when I try to use cat, more, or vi on it, it has a bunch of garbage. Is there anything I can use to "read" or view this file just like I might a non-binary file? I am running... (2 Replies)
Discussion started by: dsimpg1
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
Can someone help me figure out how to view directory content while I navigate directories (without having to go to the actual directory and "ls-ing" it)? Is there some keyboard shortcut for this? For instance, it would be useful if I could see the content of a directory when I'm copying... (2 Replies)
Discussion started by: shelata
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have a program that get a directory name from the user, then the program should go through one by one of the file, asking the user whether to move it to another folder. I tried to list the time of the file one by one. But it seems like it doesn't work. The code is as follow:
check()
{... (10 Replies)
Discussion started by: mInGzaiii
10 Replies
7. Shell Programming and Scripting
Hey,
I know the head and tail function is to view like the top or bottom lines for each file. But lets say I want to view the top/bottom 100 or top/bottom 1000 for a file. whats the command that I use to do this?
thanks (2 Replies)
Discussion started by: kylle345
2 Replies
8. UNIX for Advanced & Expert Users
Hi all,
When I use BDF command on this particular server, it outputs mostly normal stuff. However, there is one directory it can't read at all.
Also, it doesn't seem to exist.
When I BDF my file system with a small panic script (it happens even if you use just the bdf command):
As you... (17 Replies)
Discussion started by: zixzix01
17 Replies
9. Shell Programming and Scripting
I have a file name as logfiles_tar.tgz. How can I view the contents of the log files present in logfiles_tar.tgz ? Any help would be really appreciated.
Thanks (3 Replies)
Discussion started by: bobby1015
3 Replies
10. UNIX for Dummies Questions & Answers
What is the command line for viewing the sizes(lines and bytes)of all the files in your present working directory?
Is it
>ls -la (2 Replies)
Discussion started by: Payton2704
2 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). The default
value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that
job's queue, or because more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it.
All other queues can have up to 100 jobs running simultaneously. They will be run with a value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE
queuedefs(4)