How to ignore No such file or directory on the output?
Hello -
I have a script which looks for filesystem usage and its a common script for all servers I have . On few servers, we do not have a FS available and getting the output as
, which is expected. I am not in favor of having an if condition to have list of servers added and verify for that specific FS only on those servers.
wondering if there is a way I can ignore this error to show-up on output itself when someone run that script?
Noe - I write the output of the script to a temp txt file and use it for different purpose.
Hi,
I'm creating a shell script to dynamically create a recreate controlfile for an Oracle database. I need to read a cold backup file system, and make some changes to these files.
Let's say for argument sake the directory name is /ebsprod_c/oradata and it looks like this:... (6 Replies)
Noob question!
I know almost nothing so far, and I'm trying to teach myself from books, on a typical command line without using scripts how would I append output from a sort to a file in a completely different directory?
example:
If I'm sorting a file in my documents directory but I... (2 Replies)
Hello,
I know find can be prevented from recursing into directories with something like the following...
find . -name .svn -prune -a type d
But how can I completely prevent directories of a certain name (.svn) from being displayed at all, the top level and the children?
I really... (2 Replies)
Hi all........
Plss do help me.......in a big trouble... :wall::wall::wall:
I have 3 directories named as :1. /home/shuchi/source
2./home/shuchi/destination
3./home/shuchi/filter
now the problem is /home/shuchi/source has say 2 files with extension .txt as given below :
A.txt
Code:
... (0 Replies)
Hi all........
Plss do help me.......in a big trouble... :wall::wall::wall:
I have 3 directories named as :1. /home/shuchi/source
2./home/shuchi/destination
3./home/shuchi/filter
now the problem is /home/shuchi/source has say 2 files with extension .txt as given below :
A.txt
msisdn ... (5 Replies)
Dear All,
I am using find command
find /my_rep/*/RKYPROOF/*/*/WDM/HOME_INT/PWD_DATA -name rk*myguidelines*.pdf -print
The problem i am facing here is find /my_rep/*/
the directory after my_rep could be mice001, mice002 and mice001_PO, mice002_PO
i want to ignore mice***_PO directory... (3 Replies)
i am trying to recursively save a remote FTP server but exclude the files immediately under a directory directory1
wget -r -N ftp://user:pass@hostname/directory1
I want to keep these which may have more files under them
directory1/dir1/file.jpg
directory1/dir2/file.jpg... (16 Replies)
I am trying to apply an awk action over multiple files in a directory. It is a simple action, I want to print out the 1st 2 columns (i.e. $1 and $2) in each tab-separated document and output the result in a new file *.pp
This is the awk that I have come up with so far, which is not giving me a... (6 Replies)
I am using aix. I would like to ignore the /u directory. I tried this but it is not working.
find / -type f -type d \( -path /u \) -prune -o -name '*rpm*' 2>/dev/null
/u/appx/ls.rpm
/u/arch/vim.rpm (4 Replies)
Discussion started by: cokedude
4 Replies
LEARN ABOUT SUSE
sievec
SIEVEC(1) General Commands Manual SIEVEC(1)NAME
sievec - Sieve script compiler for the Dovecot secure IMAP server
SYNOPSIS
sievec [-d] [-x "extension extension ..."] script-file [out-file]
DESCRIPTION
The sievec command is part of the Sieve implementation for the Dovecot secure IMAP server. Sieve (RFC 5228) is a simple and highly extensi-
ble language for filtering e-mail messages. It can be implemented for any type of mail access protocol, mail architecture and operating
system. The language cannot execute external programs and in its basic form it does not provide the means to cause infinite loops, making
it suitable for running securely on mail servers where mail users have no permission run arbitrary programs.
Using the sievec command, Sieve scripts can be compiled into a binary representation. The resulting binary can be used directly to process
e-mail messages during the delivery process. The delivery of mail messages and therefore also the execution of Sieve scripts is performed
by Dovecot's local delivery agent (LDA) called deliver. Usually, it is not necessary to compile the Sieve script manually using sievec,
because deliver will do this automatically if the binary is missing. However, in some cases deliver does not have permission to write the
compiled binary to disk, forcing it to recompile the script every time it is executed. Using the sievec tool, this can be performed manu-
ally by an authorized user to increase performance.
The sievec command accepts two arguments: the script-file argument specifies the script to be compiled and the out-file argument specifies
where the (binary) output is to be written. This Sieve implementation reconizes files with a .sieve extension as Sieve scripts and corre-
sponding files with a .svbin extension as the associated compiled binary. This means for example that Dovecot's deliver process will look
for a binary file 'dovecot.svbin' when it needs to execute 'dovecot.sieve'. Such filename is chosen automatically for the binary output
when the out-file argument is missing.
If the script-file argument is a directory, all files in that directory with a .sieve extension are compiled into a corresponding .svbin
binary file. The compilation is not halted upon errors; it attempts to compile as many scripts in the directory as possible. Note that the
-d option and the out-file argument are not allowed when the script-file argument is a directory.
The sievec command is also useful to verify Sieve scripts before using. Additionally, with the -d option it can output a textual (and thus
human-readable) dump of the generated Sieve code to the specified file. The output is then identical to what the sieved(1) command produces
for a stored binary file. This output is mainly useful to find bugs in the compiler that yield corrupt binaries.
OPTIONS -d Don't write the binary to out-file, but write a textual dump of the binary in stead. In this context, the out-file value '-' has
special meaning: it causes the the textual dump to be written to stdout. The out-file argument may also be omitted, which has the
same effect as '-'. The output is identical to what the sieved(1) command produces for a compiled Sieve binary file. Note that this
option is not allowed when the out-file argument is a directory.
-x "extension extension ..."
Set the available extensions. The parameter is a space-separated list of the active extensions. By prepending the extension identi-
fiers with + or -, extensions can be included or excluded relative to the default set of extensions. If no extensions have a + or -
prefix, only those extensions that are explicitly listed will be enabled. Unknown extensions are ignored and a warning is produced.
By default, all supported extensions are available, except for deprecated extensions or those that are still under development.
For example -x "+imapflags -enotify" will enable the deprecated imapflags extension along with all extensions that are available by
default, except for the enotify extension.
AUTHOR
The Sieve implementation for Dovecot was written by Stephan Bosch <stephan@rename-it.nl>.
Dovecot was written by Timo Sirainen <tss@iki.fi>.
SEE ALSO sieved(1), sieve-test(1)
4 July 2009 SIEVEC(1)