How to walk through a config file with /bin/sh Post: 302347672

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/bin/sh: /usr/bin/vi: No such file or directory when doing crontab

I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,...

2. Programming

ftw/nftw -- filesystem tree walk

Hi, I recently experimented with ftw() and nftw(). These are function for calling some function for every file in a subtree. I need to get full information about type of file. Almost everything is working according to documentation but I noticed following problem: With a value FTW_PHYS...

3. UNIX for Dummies Questions & Answers

fuser: difference with bin/sh and bin/ksh shell script

Hi, I have a problem I don't understand with fuser. I launch a simple shell script mysleep.sh: I launch the command fuser -fu mysleep.sh but fuser doesn't return anything excepted: mysleep: Then I modify my script switching from #!/bin/sh to #!/bin/ksh I launch the command fuser -fu...

4. Shell Programming and Scripting

parsing config file to create new config files

Hi, I want to use a config file as the base file and parse over the values of country and city parameters in the config file and generate separate config files as explained below. I will be using the config file as mentioned below: (config.txt) country:a,b city:1,2 type:b1...

5. Shell Programming and Scripting

Shell script that will compare two config files and produce 2 outputs 1)actual config file 2)report

Hi I am new to shell scripting. There is a requirement to write a shell script to meet follwing needs.Prompt reply shall be highly appreciated. script that will compare two config files and produce 2 outputs - actual config file and a report indicating changes made. OS :Susi linux ver 10.3. ...

6. OS X (Apple)

When to use /Users/m/bin instead of /usr/local/bin (& whats the diff?)?

Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself. But what about the directory I didn't create, namely /Users/m/bin? How is that directory...

7. HP-UX

SNMP Walk need to enable

We are using a third party to monitor unix servers performance since last 60 days, since last 3 days we are not able to get the performance alarms on our tool. When we check the same with the tool team, they said "SNMP walk is not happening for all the servers." Performance we mean...

8. Shell Programming and Scripting

Usage of #!/bin/sh vs #!/bin/bash shell scripts?

Some question about the usage of shell scripts: 1.) Are the commands of the base shell scripts a subset of bash commands? 2.) Assume I got a long, long script WITHOUT the first line. How can I find out if the script was originally designed f�r "sh" or "bash"? 3.) How can I check a given...

LEARN ABOUT MOJAVE

ppi::token::comment

PPI::Token::Comment(3)					User Contributed Perl Documentation				    PPI::Token::Comment(3)

NAME

       PPI::Token::Comment - A comment in Perl source code

INHERITANCE

	 PPI::Token::Comment
	 isa PPI::Token
	     isa PPI::Element

SYNOPSIS

	 # This is a PPI::Token::Comment

	 print "Hello World!"; # So it this

	 $string =~ s/ foo  # This, unfortunately, is not :(
	       bar
	       /w;

DESCRIPTION

       In PPI, comments are represented by "PPI::Token::Comment" objects.

       These come in two flavours, line comment and inline comments.

       A "line comment" is a comment that stands on its own line. These comments hold their own newline and whitespace (both leading and trailing)
       as part of the one "PPI::Token::Comment" object.

       An inline comment is a comment that appears after some code, and continues to the end of the line. This does not include whitespace, and
       the terminating newlines is considered a separate PPI::Token::Whitespace token.

       This is largely a convenience, simplifying a lot of normal code relating to the common things people do with comments.

       Most commonly, it means when you "prune" or "delete" a comment, a line comment disappears taking the entire line with it, and an inline
       comment is removed from the inside of the line, allowing the newline to drop back onto the end of the code, as you would expect.

       It also means you can move comments around in blocks much more easily.

       For now, this is a suitably handy way to do things. However, I do reserve the right to change my mind on this one if it gets dangerously
       anachronistic somewhere down the line.

METHODS

       Only very limited methods are available, beyond those provided by our parent PPI::Token and PPI::Element classes.

   line
       The "line" accessor returns true if the "PPI::Token::Comment" is a line comment, or false if it is an inline comment.

SUPPORT

       See the support section in the main module.

AUTHOR

       Adam Kennedy <adamk@cpan.org>

COPYRIGHT

       Copyright 2001 - 2011 Adam Kennedy.

       This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

       The full text of the license can be found in the LICENSE file included with this module.

perl v5.18.2							    2011-02-25						    PPI::Token::Comment(3)