05-02-2008
Thank you, Thank you, Thank you!
I had the 'then', just forgot to put it in the pseudo-code, but the semi-colon was the key. Thanks so much! I've wrestled with this for days.
Is the semi-colon always needed in an if statement? I've been reading O'Reilly's Classic Shell Scripting and it doesn't mention the semi-colon at all. What gives?
10 More Discussions You Might Find Interesting
1. Linux
We have requirments to not allow a userid login abilities but allow users to 'su' to it. In solaris I normally set the shell in /etc/passwd to bin/false. THis does not work on Linux, any suggestions would help. (1 Reply)
Discussion started by: bryanthomas
1 Replies
2. Shell Programming and Scripting
i want to delete every newline and every line which starts with "RECORD......." in a file.
FILE:
Record 61391 in base BROCKHAUS (Timestamp: 2008-04-09 11:38:38)
UNTERTITEL :
Gräfin (seit 1707 Reichsgräfin) von, * Schwerin 4. 2. 1686, + Berlin
21. 10. 1744; wurde
Record 61392 in base BROCKHAUS... (4 Replies)
Discussion started by: trek
4 Replies
3. UNIX for Advanced & Expert Users
helo
helo I have create user for the group and entry for the user in /etc/passwd file is liek this
bhavin:x:2014:109:test:/home/pds_RBAC:/bin/false
I have keep here /bin/false
now i m accesing user through sftp
ow when i access that user using sftp from the another linux pc
for e.g... (1 Reply)
Discussion started by: amitpansuria
1 Replies
4. Solaris
Hi Experts,
I am using Solaris-10, Sun-Fire-V445.
i got often the below message-
"Memory Usage – Critical, Memory usage (RAM) exceeding 90%
The memory utilization is exceeding 90%" in a application running on solaris.
I checked with Vmstat. Everything seems to be fine. Where i should... (5 Replies)
Discussion started by: thepurple
5 Replies
5. Shell Programming and Scripting
Just started with learning python and tried something, most people here would call more than simple.
I just wanted to list all directories within my main directory. So I user the following code:
#!/usr/bin/env python
import os
if os.path.isdir("/home/testaccaunt/public_html"):
... (8 Replies)
Discussion started by: medic
8 Replies
6. Shell Programming and Scripting
Hi All,
I am using the below Script to enter a line in the File:
#!/bin/ksh
# To delete the last line if it contains the pattern Redirect permanent / Virgin Atlantic Airways - Popup
echo "Enter the URL that should point to the particular microsite"
read url
# To delete the last line if it... (0 Replies)
Discussion started by: Shazin
0 Replies
7. IP Networking
Why this happens?
How to solve this?
$netstat -na |grep 9325
tcp 0 0 127.0.0.1:9325 127.0.0.1:9325 ESTABLISHED
When a client socket repeatedly tries to connect to an inactive(no server socket is listening on this port) local port,connect succeeds.
... (1 Reply)
Discussion started by: johnbach
1 Replies
8. AIX
Checking configuration access files for an AIX server, left me wondering about this :confused::
If a user is added to system group, it gets gid=0 with some security risks because it gets some root kind of file access level.
Is this insecure condition kept if the user has admin variable... (0 Replies)
Discussion started by: bkiddo
0 Replies
9. Shell Programming and Scripting
I have this code that sometimes return a false value and the code inside the if statement gets executed and error out. Any idea why? thanks.
So I set a debug and see what the value for $ScriptElapsedTime
Here is the value I got ScriptElapsedTime='03:20'. Base on this value the if... (10 Replies)
Discussion started by: nugent
10 Replies
10. Shell Programming and Scripting
Hi
I have written a script to send email alerts when load of my linux server reaches max point
I keep getting false emails thought the load is normal , looks like same email is generated again and again - called from cron tab
checked if the tempfile is present , no it is not , cleaned... (22 Replies)
Discussion started by: anil529
22 Replies
LEARN ABOUT DEBIAN
regexp::common::uri::ftp
Regexp::Common::URI::ftp(3pm) User Contributed Perl Documentation Regexp::Common::URI::ftp(3pm)
NAME
Regexp::Common::URI::ftp -- Returns a pattern for FTP URIs.
SYNOPSIS
use Regexp::Common qw /URI/;
while (<>) {
/$RE{URI}{FTP}/ and print "Contains an FTP URI.
";
}
DESCRIPTION
$RE{URI}{FTP}{-type}{-password};
Returns a regex for FTP URIs. Note: FTP URIs are not formally defined. RFC 1738 defines FTP URLs, but parts of that RFC have been
obsoleted by RFC 2396. However, the differences between RFC 1738 and RFC 2396 are such that they aren't applicable straightforwardly to FTP
URIs.
There are two main problems:
Passwords.
RFC 1738 allowed an optional username and an optional password (separated by a colon) in the FTP URL. Hence, colons were not allowed in
either the username or the password. RFC 2396 strongly recommends passwords should not be used in URIs. It does allow for userinfo
instead. This userinfo part may contain colons, and hence contain more than one colon. The regexp returned follows the RFC 2396
specification, unless the {-password} option is given; then the regex allows for an optional username and password, separated by a
colon.
The ;type specifier.
RFC 1738 does not allow semi-colons in FTP path names, because a semi-colon is a reserved character for FTP URIs. The semi-colon is
used to separate the path from the option type specifier. However, in RFC 2396, paths consist of slash separated segments, and each
segment is a semi-colon separated group of parameters. Straigthforward application of RFC 2396 would mean that a trailing type
specifier couldn't be distinguished from the last segment of the path having a two parameters, the last one starting with type=.
Therefore we have opted to disallow a semi-colon in the path part of an FTP URI.
Furthermore, RFC 1738 allows three values for the type specifier, A, I and D (either upper case or lower case). However, the internet
draft about FTP URIs [DRAFT-FTP-URL] (which expired in May 1997) notes the lack of consistent implementation of the D parameter and
drops D from the set of possible values. We follow this practise; however, RFC 1738 behaviour can be archieved by using the -type =
"[ADIadi]"> parameter.
FTP URIs have the following syntax:
"ftp:" "//" [ userinfo "@" ] host [ ":" port ]
[ "/" path [ ";type=" value ]]
When using {-password}, we have the syntax:
"ftp:" "//" [ user [ ":" password ] "@" ] host [ ":" port ]
[ "/" path [ ";type=" value ]]
Under "{-keep}", the following are returned:
$1 The complete URI.
$2 The scheme.
$3 The userinfo, or if {-password} is used, the username.
$4 If {-password} is used, the password, else "undef".
$5 The hostname or IP address.
$6 The port number.
$7 The full path and type specification, including the leading slash.
$8 The full path and type specification, without the leading slash.
$9 The full path, without the type specification nor the leading slash.
$10 The value of the type specification.
REFERENCES
[DRAFT-URL-FTP]
Casey, James: A FTP URL Format. November 1996.
[RFC 1738]
Berners-Lee, Tim, Masinter, L., McCahill, M.: Uniform Resource Locators (URL). December 1994.
[RFC 2396]
Berners-Lee, Tim, Fielding, R., and Masinter, L.: Uniform Resource Identifiers (URI): Generic Syntax. August 1998.
SEE ALSO
Regexp::Common::URI for other supported URIs.
AUTHOR
Damian Conway (damian@conway.org)
MAINTAINANCE
This package is maintained by Abigail (regexp-common@abigail.be).
BUGS AND IRRITATIONS
Bound to be plenty.
LICENSE and COPYRIGHT
This software is Copyright (c) 2001 - 2009, Damian Conway and Abigail.
This module is free software, and maybe used under any of the following licenses:
1) The Perl Artistic License. See the file COPYRIGHT.AL.
2) The Perl Artistic License 2.0. See the file COPYRIGHT.AL2.
3) The BSD Licence. See the file COPYRIGHT.BSD.
4) The MIT Licence. See the file COPYRIGHT.MIT.
perl v5.14.2 2010-02-23 Regexp::Common::URI::ftp(3pm)