I have a lot of script files that were created by Extract in a dir that no longer exists. Now that I have to run these scripts they 'all' have to be changed. I'm looking for a way to do a 'mass' change if possible.
So far, I've dumped all of the script file names to a file and sorted them to... (5 Replies)
I am having a shell script that connects to database half hourly and pulls out the backlog from some tables. Now that logfile is growing too big and I need to housekeep it! effectively I want to keep last 30 days data in that file and move rest to archived file.
The file contents are as below.... (14 Replies)
/\/\*/!b
:x
/\*\//!{
N
bx
}
s/\/\*.*\*\///
This scipt should remove c like commnets /**/
i know what de last line does
but i dont't know what the first lines do
Can anyone explain please (3 Replies)
I am trying to run a sed command within a script to edit a file.
I am trying to put the value of MYUSER into the sshd_config file.
Instead of putting the value of the variable, MYUSER, it puts in the string ${MYUSER}.
Anyone know a good solution to this?
cat ${SSHD_CONFIG} | sed... (1 Reply)
:rolleyes:
I have a series of folders /temp/a /temp/b /temp/c
In folders a, b, and c, I have files
a1.txt..........a20.txt
b1.txt..........b40.txt &
c1.txt..........c60.txt
Each file has the same data format :-
Line... (2 Replies)
I'm trying to write a simple script that replaces a string. The script works for uninterrupted strings, but as soon as sed encounters a space it stops reading the new string. I've tried double quotations in sed and backslashes before the $, however these don't work. Below is the script. Any help... (9 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Create a sed script that will display a list of all users in the /etc/passwd file that belong to the group... (0 Replies)
I am beginner for Unix. I practicing unix shell script. I worked out some sed script example from internet. Everything fine.
But in real unix environment, where sed script is mainly used.?
Can anyone give some examples for the usage of sed script in real unix environment. It will be useful for... (1 Reply)
Hi ,
i am stuck in this simple script.
#!/bin/ksh
echo "enter the file name"
read flname
echo "enter version"
read ver
grep $flname /home/con/snsc/perl/map > flplist
dirname `cat flplist` | sed 's/\/so${vers}\//\/so${vers}_xyz\//' > dirlist
the map file is basically a list of file... (3 Replies)
I am having a file as stated below :
File 1:
##########################
idnd a
integer 2;
list 1 ;
list2 ;
chip top alist( .a(1) , .b(2) , .c(3) ,
.d(1) , .e(7) , .n(80),
.d(1) , .g(7) , .n(80),
.f(1) , .e(7) , .m(80));
lis 7 nfj ;
jdjd kn;
jsjd l ; (4 Replies)
Discussion started by: kshitij
4 Replies
LEARN ABOUT MOJAVE
pod::parselink5.18
Pod::ParseLink(3pm) Perl Programmers Reference Guide Pod::ParseLink(3pm)NAME
Pod::ParseLink - Parse an L<> formatting code in POD text
SYNOPSIS
use Pod::ParseLink;
my ($text, $inferred, $name, $section, $type) = parselink ($link);
DESCRIPTION
This module only provides a single function, parselink(), which takes the text of an L<> formatting code and parses it. It returns the
anchor text for the link (if any was given), the anchor text possibly inferred from the name and section, the name or URL, the section if
any, and the type of link. The type will be one of "url", "pod", or "man", indicating a URL, a link to a POD page, or a link to a Unix
manual page.
Parsing is implemented per perlpodspec. For backward compatibility, links where there is no section and name contains spaces, or links
where the entirety of the link (except for the anchor text if given) is enclosed in double-quotes are interpreted as links to a section
(L</section>).
The inferred anchor text is implemented per perlpodspec:
L<name> => L<name|name>
L</section> => L<"section"|/section>
L<name/section> => L<"section" in name|name/section>
The name may contain embedded E<> and Z<> formatting codes, and the section, anchor text, and inferred anchor text may contain any
formatting codes. Any double quotes around the section are removed as part of the parsing, as is any leading or trailing whitespace.
If the text of the L<> escape is entirely enclosed in double quotes, it's interpreted as a link to a section for backward compatibility.
No attempt is made to resolve formatting codes. This must be done after calling parselink() (since E<> formatting codes can be used to
escape characters that would otherwise be significant to the parser and resolving them before parsing would result in an incorrect parse of
a formatting code like:
L<verticalE<verbar>barE<sol>slash>
which should be interpreted as a link to the "vertical|bar/slash" POD page and not as a link to the "slash" section of the "bar" POD page
with an anchor text of "vertical". Note that not only the anchor text will need to have formatting codes expanded, but so will the target
of the link (to deal with E<> and Z<> formatting codes), and special handling of the section may be necessary depending on whether the
translator wants to consider markup in sections to be significant when resolving links. See perlpodspec for more information.
SEE ALSO
Pod::Parser
The current version of this module is always available from its web site at <http://www.eyrie.org/~eagle/software/podlators/>.
AUTHOR
Russ Allbery <rra@stanford.edu>.
COPYRIGHT AND LICENSE
Copyright 2001, 2008, 2009 Russ Allbery <rra@stanford.edu>.
This program is free software; you may redistribute it and/or modify it under the same terms as Perl itself.
perl v5.18.2 2013-11-04 Pod::ParseLink(3pm)