Search Results

perldoc DBI will reveal the following snippet

#!/usr/bin/perl

use strict;
use DBI();

# Connect to the database.
my $dbh = DBI->connect("DBI:mysql:database=test;host=localhost",...

if["$1-l"] Try
if [ "$1" == "-l" ] ...spaces and all, you need a space between "if" and "[" for it to work. The same goes for your "-d" statement up there, the spaces are important.

for filename in "$1"/*
do
if [ -f "$filename" ] && [ ! -e "$filename.old" ]; then
mv "$filename" "$filename.old"
fi
done

No, You don't need loop. either one-liner can do the job.

could use -v option of grep command to exclude .old files.And those curly braces are important when you append any letter or word (here: .old)

for filename in $(ls * | grep -v '\.old$' 2>...

find $1 -maxdepth 1 -type f -not -name "*.old" -exec mv {} {}.old \;



find $1 -maxdepth 1 -type f -not -name "*.old" | xargs -i{} mv {} {}.old

Put the cd and ls in (). cd changes your working directory, $(pwd) = $PWD, the base of all relative paths.

The parentheses mean the cd moves a subshell but not the parent shell. If you cd dir1; cd dir2with relative paths, you are not in dir2, you are in dir1/dir2 -- you are digging down an imaginary...

To run in other directories requires that the other directories to be other ( or world) r-x
or r-x for the group you are in.

Most system ( e.g. /usr or /opt) directories are readable.

Have you tried diff?

I like comm for this sort of thing, too.

Cd to the dir in a subshell so the file names are barefoot.

Changing directory means any files, including executable files, in the old dir are no longer available without a prefix. If you were and /a/b/ and run c, which is /a/b/c, then when you change dir to...

As you are a novice, perhaps you have not grasped UNIX pathing: file locations can be relative to your current directory $PWD, initially $HOME where you log in, but also absolute (starting with /)....

( cd $2 ; ls -ld $file )