Hi,
I'm working on a shell script that reports service status on a database server.
There are some services that are in disabled status that the script should ignore and only check the services that are in Enabled status.
I output the service configuration to a file and use that information to... (5 Replies)
.......
06/09/2013|12:00:00 PM|3|26112|40|44032|27419.7|6 1 0 93 |6|1|0|93
06/09/2013|12:30:00 PM|3|26112|40|44032|27491|11 4 0 85 |11|4|0|85
I have "sysperf.out" file containing the lines above.
What I like to have on the output is:
Node: prod1db ===> this is the hostname
Date:... (7 Replies)
Hi,
I must be overlooking something, but I don't understand why this doesn't work. I'm trying to grep on a date, excluding all the lines starting with a dash:
testfile:
#2013-12-31
2013-12-31code:
grep '^2013-12-31' testfileI'm expecting to see just the second line '2013-12-31' but I don't... (3 Replies)
Hi,
Below is the command to grep for a string under
grep -r "redeem" /home/tom
Need to make it case insensitive and exclude logs & tmp folders under /home/tom directory in my Search.
Need this in Linux. (1 Reply)
I wrote this korn script and ran into a hole. I can use find to exclude all the hidden directories and to use my include file/exclude files for running a full backup
find / -depth -ipath '/home/testuser/.*' -prune -o -print| grep -f include.mydirs | grep -v -f exclude.mydirs
but when I... (8 Replies)
I must write a script to change all C++ like comments:
// this is a comment
to this one
/* this is a comment */
How to do it by sed? With file:
#include <cstdio>
using namespace std; //one
// two
int main() {
printf("Example"); // three
}//four
the result should be: (2 Replies)
Hello, I'm trying to use grep or egrep to exclude a whole range of characters but how do I exclude both a single and a double quote.
It might be easier to say how do I use grep to find both single and double quotes.
grep ' ' " ' file
grep detects the first single quote within my... (4 Replies)
I am doing "ps -f" to see my process.
but I get lines that one of it represents the ps command itself.
I want to grep it out using -v flag, but than I get another process that belongs to the GREP itself :
I would like to exclude
# ps -f
UID PID PPID C STIME TTY TIME CMD... (2 Replies)
11132
13069
11137
11142
13070
Can I use grep command to exclude all lines beginning with 13?
I dont want to use grep -v 13 as potentially there will be a number with something like 11013 that I would exclude in error.. (2 Replies)
indent(1) General Commands Manual indent(1)Name
indent - indent and format C program source
Syntax
indent input [output] [flags]
Description
The command is intended primarily as a C program formatter. Specifically, indents code lines, aligns comments, inserts spaces around oper-
ators where necessary and breaks up declaration lists as in ``int a,b,c;''.
The command does not break up long statements to make them fit within the maximum line length, but it does flag lines that are too long.
Lines are broken so that each statement starts a new line, and braces appear alone on a line. Also, an attempt is made to line up identi-
fiers in declarations.
The flags that can be specified follow. They can appear before or after the file names. If the output file is omitted, the formatted file
is written back into input and a ``backup'' copy of input is written in the current directory. If input is named ``/blah/blah/file'', the
backup file is named ``.Bfile''. If output is specified, checks to make sure it is different from input.
Options
The following options are used to control the formatting style imposed by
-lnnn Determines maximum length of output line. The default is 75.
-cnnn Determines column in which comments start. The default is 33.
-cdnnn Determines column in which comments on declarations start. The default is for these comments to start in the same column as
other comments.
-innn Determines number of spaces for one indentation level. The default is 4.
-dj,-ndj Causes declarations to be left justified. -ndj causes them to be indented the same as code. The default is -ndj.
-v,-nv -v turns on ``verbose'' mode, -nv turns it off. When in verbose mode, reports when it splits one line of input into two or
more lines of output, and it gives some size statistics at completion. The default is -nv.
-bc,-nbc Forces newline after each comma in a declaration. -nbc turns off this option. The default is -bc.
-dnnn Controls the placement of comments which are not to the right of code. Specifying -d2 means that such comments are placed two
indentation levels to the left of code. The default -d0 lines up these comments with the code. See the section on comment
indentation below.
-br,-bl Specifying -bl causes complex statements to be lined up in a space order. For example,
if (...)
{
code
}
Specifying -br (the default) makes them look like this:
if (...) {
code
}
You may set up your own ``profile'' of defaults to by creating the file ``.indent.pro'' in your login directory and including whatever
switches you like. If is run and a profile file exists, then it is read to set up the program's defaults. Switches on the command line,
though, always override profile switches. The profile file must be a single line of not more than 127 characters. The switches should be
separated on the line by spaces or tabs.
Multiline expressions
The command does not break up complicated expressions that extend over multiple lines. However, it usually indents such expressions that
have already been broken up correctly. Such an expression might look like the following:
x =
(
(Arbitrary parenthesized expression)
+
(
(Parenthesized expression)
*
(Parenthesized expression)
)
);
Comments
The command recognizes the following four kinds of comments:
1) straight text
2) ``box'' comments
3) UNIX-style comments
4) comments that should be passed through unchanged
The comments are interpreted as follows:
``Box'' comments The command assumes that any comment with a dash immediately after the start of comment (i.e. ``/*-'') is a comment
surrounded by a box of stars. Each line of such a comment is left unchanged, except that the first non-blank character
of each successive line is lined up with the beginning slash of the first line. Box comments are indented (see below).
``Unix-style'' comments
This is the type of section header which is used extensively in the UNIX system source. If the start of comment
(``/*'') appears on a line by itself, assumes that it is a UNIX-style comment. These are treated similarly to box com-
ments, except the first non-blank character on each line is lined up with the `*' of the ``/*''.
Unchanged comments Any comment which starts in column 1 is left completely unchanged. This is intended primarily for documentation header
pages. The check for unchanged comments is made before the check for UNIX-style comments.
Straight text All other comments are treated as straight text. Indent fits as many words (separated by blanks, tabs, or new lines)
on a line as possible. Straight text comments are indented.
Comment indentation
Box, UNIX-style, and straight text comments may be indented. If a comment is on a line with code it is started in the ``comment column'',
which is set by the -cnnn command line parameter. Otherwise, the comment is started at nnn indentation levels less than where code is cur-
rently being placed, where nnn is specified by the -dnnn command line parameter. (Indented comments is never be placed in column 1.) If
the code on a line extends past the comment column, the comment is moved to the next line.
Restrictions
Does not know how to format ``long'' declarations.
Diagnostics
Diagnostic error messages, mostly to tell that a text line has been broken or is too long for the output line.
Files
.indent.pro profile file
indent(1)