Thank you, Aia, for posting! Sorry for the confusion...
Here's the program flow which I am seeking to achieve with my crude little snippet:
Begin by printing the word "starting" to the terminal.
Check ~/.somedir using while() to see if the file "testFile" is present.
If it is, send the phrase "file detected" to the terminal; and loop back again to check if "testFile" is still present after a 1-second timeout.
If "testFile" doesn't exist on ~/.somedir, print the phrase "file missing" to the terminal and exit.
Not too exciting; but I think it about encapsulates what I need to do
To this end, I have formed three different while() statements to interchangeably fit into the main script code:
The commandlines from 1) and 2) both work well as stand-alone code at the terminal; but do not execute properly from Perl. #2 is particularly well-suited to the work; as it doesn't rely upon the file being of any particular size to allow for successful detection. String comparisons should logically work as expected in this context.
Choice #3 is preferred as a straightforward solution; but, unfortunately, Perl will not find our "testFile" on a hidden directory such as ~/.somedir using the normal
statement layout.
So, that's the problem in a nutshell...
Again, I'd prefer going with the straight-Perl approach which #3 offers. But, if making this work is more complicated than getting the commandline in
to function correctly in this code context, I'll settle for a just "quick fix" of #2 for now.
I have never heard of this before but someone at work here says there is a command to find files that are under currently mounted filesystems. Does anyone know what this command is and is it available on HP-UX? (3 Replies)
Hi. I have a script which is deleting files with a particular extension and older than 45 days.The code is:
find <path> -name "<filename_pattern>" -mtime +45 -exec rm {} \;
But the problem is that some important files are also getting deleted.To prevent this I have decide to make a dummy... (4 Replies)
Hi Guys,
I need to count files in a dir which were updated yesterday.
ls -lth | grep -i 'Jul 7' | wc -l
The dir holds files of last 15 days and total count is as 2067476.
Is it efficient to count the files using perl? I have developed the following perl script making use of system().
Can... (3 Replies)
I have written a script to secure delete all files in a quarantine folder and my Trash folder. All the commands run trough Terminal via the script.
The problem I am having is when I am changing the directory to the hidden Trash folder. When I do cd /Users/WatsonN/.Trash all it does is take it to... (2 Replies)
I have an application consisting of a number of perl files. I want to find those perl files that have no documentation yet, so I tried the following from the root level of the directory where the application resides:
perldoc -r *
The output is something like the following:
No documentation found... (2 Replies)
Hi,
Me i ask if someone knows about this hidden directory or it me knows where this dir associated with or in a program.
I had and notices this .awo dir with bin files inside title 6770669_info.eeesync files in my directory. I wonder if this is associated with my backup program or any program... (0 Replies)
I am completely new to perl programming. My father is helping me learn said programming language. However, I am stuck on one of the assignments he has given me, and I can't find very much help with it via google, either because I have a tiny attention span, or because I can be very very dense.
... (4 Replies)
I'm writing a Perl script which has its 1st step as to copy files from one directory to another directory. The Source directory has got files with extension, without extension, directories etc. But I want to copy ONLY files with no extension. The files with extensions and directories should not get... (2 Replies)
Hello.
I use this command :
rsync -av --include=".*" --dry-run "$A_FULL_PATH_S" "$A_FULL_PATH_D"The data comes from the output of a find command.
And no full source directories are in use, only some files.
Source example... (2 Replies)
Discussion started by: jcdole
2 Replies
LEARN ABOUT OSX
path::class
Path::Class(3) User Contributed Perl Documentation Path::Class(3)NAME
Path::Class - Cross-platform path specification manipulation
VERSION
version 0.26
SYNOPSIS
use Path::Class;
my $dir = dir('foo', 'bar'); # Path::Class::Dir object
my $file = file('bob', 'file.txt'); # Path::Class::File object
# Stringifies to 'foo/bar' on Unix, 'fooar' on Windows, etc.
print "dir: $dir
";
# Stringifies to 'bob/file.txt' on Unix, 'bobfile.txt' on Windows
print "file: $file
";
my $subdir = $dir->subdir('baz'); # foo/bar/baz
my $parent = $subdir->parent; # foo/bar
my $parent2 = $parent->parent; # foo
my $dir2 = $file->dir; # bob
# Work with foreign paths
use Path::Class qw(foreign_file foreign_dir);
my $file = foreign_file('Mac', ':foo:file.txt');
print $file->dir; # :foo:
print $file->as_foreign('Win32'); # foofile.txt
# Interact with the underlying filesystem:
# $dir_handle is an IO::Dir object
my $dir_handle = $dir->open or die "Can't read $dir: $!";
# $file_handle is an IO::File object
my $file_handle = $file->open($mode) or die "Can't read $file: $!";
DESCRIPTION
"Path::Class" is a module for manipulation of file and directory specifications (strings describing their locations, like
'/home/ken/foo.txt' or 'C:WindowsFoo.txt') in a cross-platform manner. It supports pretty much every platform Perl runs on, including
Unix, Windows, Mac, VMS, Epoc, Cygwin, OS/2, and NetWare.
The well-known module "File::Spec" also provides this service, but it's sort of awkward to use well, so people sometimes avoid it, or use
it in a way that won't actually work properly on platforms significantly different than the ones they've tested their code on.
In fact, "Path::Class" uses "File::Spec" internally, wrapping all the unsightly details so you can concentrate on your application code.
Whereas "File::Spec" provides functions for some common path manipulations, "Path::Class" provides an object-oriented model of the world of
path specifications and their underlying semantics. "File::Spec" doesn't create any objects, and its classes represent the different ways
in which paths must be manipulated on various platforms (not a very intuitive concept). "Path::Class" creates objects representing files
and directories, and provides methods that relate them to each other. For instance, the following "File::Spec" code:
my $absolute = File::Spec->file_name_is_absolute(
File::Spec->catfile( @dirs, $file )
);
can be written using "Path::Class" as
my $absolute = Path::Class::File->new( @dirs, $file )->is_absolute;
or even as
my $absolute = file( @dirs, $file )->is_absolute;
Similar readability improvements should happen all over the place when using "Path::Class".
Using "Path::Class" can help solve real problems in your code too - for instance, how many people actually take the "volume" (like "C:" on
Windows) into account when writing "File::Spec"-using code? I thought not. But if you use "Path::Class", your file and directory objects
will know what volumes they refer to and do the right thing.
The guts of the "Path::Class" code live in the "Path::Class::File" and "Path::Class::Dir" modules, so please see those modules'
documentation for more details about how to use them.
EXPORT
The following functions are exported by default.
file
A synonym for "Path::Class::File->new".
dir A synonym for "Path::Class::Dir->new".
If you would like to prevent their export, you may explicitly pass an empty list to perl's "use", i.e. "use Path::Class ()".
The following are exported only on demand.
foreign_file
A synonym for "Path::Class::File->new_foreign".
foreign_dir
A synonym for "Path::Class::Dir->new_foreign".
Notes on Cross-Platform Compatibility
Although it is much easier to write cross-platform-friendly code with this module than with "File::Spec", there are still some issues to be
aware of.
o On some platforms, notably VMS and some older versions of DOS (I think), all filenames must have an extension. Thus if you create a
file called foo/bar and then ask for a list of files in the directory foo, you may find a file called bar. instead of the bar you were
expecting. Thus it might be a good idea to use an extension in the first place.
AUTHOR
Ken Williams, KWILLIAMS@cpan.org
COPYRIGHT
Copyright (c) Ken Williams. All rights reserved.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
Path::Class::Dir, Path::Class::File, File::Spec
perl v5.16.2 2013-08-25 Path::Class(3)