9 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
I tried to find a file lives within curent directory only, and typed
$ find . -depth 1 -ls -name *.ini
But it gave me,
find: paths must precede expression: 1
Usage: find
How'd I do it correctly ? Thanks in advance. (2 Replies)
Discussion started by: abdulbadii
2 Replies
2. Shell Programming and Scripting
Hi All,
We have SuoOs and Linux servers.
May i know how do we find the queue depth of IBM MQ from server. (2 Replies)
Discussion started by: Girish19
2 Replies
3. Windows & DOS: Issues & Discussions
A few of our users are adept at creating folders like 2015\2015 something\event\2015 event\document\2015 which makes their documents close to impossible to find. Is there any way I can restrict the depth of the folders they are allowed to create? (1 Reply)
Discussion started by: Corona688
1 Replies
4. Shell Programming and Scripting
Hi
I am trying to a write a script which gives message queue depth for every 5 mins in a file.
Commands that I use are
runmqsc QM_Name
display ql(*) curdepth
Since I can use only MQSC commands I need help on how to fetch the output on to a file after executing display command. (3 Replies)
Discussion started by: jhilmil
3 Replies
5. Shell Programming and Scripting
I was looking at a code and stumbled over the option -depth of find command
After searching what -depth does I found the below:
-depth Process each directory's contents before the directory itself.
Does it mean the sub directories are processed before the current directory in the search... (1 Reply)
Discussion started by: zulfi123786
1 Replies
6. UNIX for Dummies Questions & Answers
Good Morning,
I'm trying to write a command which copies the folder tree from a source directory to a target directory. The problem is I only want the first level of folders from the source directory, can I specify a maximum depth with rsync? Heres what I have so far:
rsync -av -f"+ */"... (2 Replies)
Discussion started by: hermiker
2 Replies
7. Programming
Hello,
I am looking for specific files in my tree directory using ftw(3). How do I know how deep I am in the file structure.. in other words, say I am looking for config.txt files, and my structure looks like this..
/some/directory/user1/config.txt
/some/directory/user2/config.txt
....... (2 Replies)
Discussion started by: germallon
2 Replies
8. Shell Programming and Scripting
I have the following script:
Now they have added on a new requirement, they only want to go to a certain depth in the directories returned. How do I code it to only go say 3 directories deeper than $DIRECTORY? (12 Replies)
Discussion started by: la_womn
12 Replies
9. Shell Programming and Scripting
hi
how to find the queue depth of MQ Queue using unix
please its very urgent (0 Replies)
Discussion started by: Satyak
0 Replies
EXPIRE.CTL(5) File Formats Manual EXPIRE.CTL(5)
NAME
expire.ctl - control file for Usenet article expiration
DESCRIPTION
The file /etc/news/expire.ctl is the default control file for the expire(8) program, which reads it at start-up. Blank lines and lines
beginning with a number sign (``#'') are ignored. All other lines should be in one of two formats.
The first format specifies how long to keep a record of fully-expired articles. This is useful when a newsfeed intermittently offers older
news that is not kept around very long. (The case of very old news is handled by the ``-c'' flag of innd(8).) There should only be one
line in this format, which looks like this:
/remember/:days
Where days is a floating-point number that specifies the upper limit to remember a Message-ID, even if the article has already expired.
(It does not affect article expirations.)
Most of the lines in the file will consist of five colon-separated fields, as follows:
pattern:modflag:keep:default:purge
The pattern field is a list of wildmat(3)-style patterns, separated by commas. This field specifies the newsgroups to which the line is
applied. Note that the file is interpreted in order, so that the last line that matches will be used. This means that general patterns
(like a single asterisk to set the defaults) should appear before specific group specifications.
The modflag field can be used to further limit newsgroups to which the line applies, and should be chosen from the following set:
M Only moderated groups
U Only unmoderated groups
A All groups
The next three fields are used to determine how long an article should be kept. Each field should be either a number of days (fractions
like ``8.5'' are allowed) or the word ``never.'' The most common use is to specify the default value for how long an article should be
kept. The first and third fields -- keep and purge -- specify the boundaries within which an Expires header will be honored. They are
ignored if an article has no Expires header. The fields are specified in the file as ``lower-bound default upper-bound,'' and they are
explained in this order. Since most articles do not have explicit expiration dates, however, the second field tends to be the most impor-
tant one.
The keep field specifies how many days an article should be kept before it will be removed. No article in the newsgroup will be removed if
it has been filed for less then keep days, regardless of any expiration date. If this field is the word ``never'' then an article cannot
have been kept for enough days so it will never be expired.
The default field specifies how long to keep an article if no Expires header is present. If this field is the word ``never'' then articles
without explicit expiration dates will never be expired.
The purge field specifies the upper bound on how long an article can be kept. No article will be kept longer then the number of days spec-
ified by this field. All articles will be removed after then have been kept for purge days. If purge is the word ``never'' then the arti-
cle will never be deleted.
It is often useful to honor the expiration headers in articles, especially those in moderated groups. To do this, set keep to zero,
default to whatever value you wish, and purge to never. To ignore any Expires header, set all three fields to the same value.
There must be exactly one line with a pattern of ``*'' and a modflags of ``A'' -- this matches all groups and is used to set the expiration
default. It should be the first expiration line.
For example,
## How long to keep expired history
/remember/:5
## Most things stay for two weeks
*:A:14:14:14
## Believe expiration dates in moderated groups, up to six weeks
*:M:1:30:42
## Keep local stuff for a long time
foo.*:A:30:30:30
HISTORY
Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews. This is revision 1.15, dated 1996/10/29.
SEE ALSO
expire(8), wildmat(3).
EXPIRE.CTL(5)
01-20-2009
