Robert wrote:
On 3/1/05 9:18 AM, in article [EMAIL PROTECTED],
"JupiterHost.Net" <[EMAIL PROTECTED]> wrote:
perldoc -f unlink
Note: "unlink" will not delete directories unless you are superuser and
the -U flag is supplied to Perl.
Have you actually done that? Normally, I do go by perldoc but in
On 3/1/05 9:18 AM, in article [EMAIL PROTECTED],
"JupiterHost.Net" <[EMAIL PROTECTED]> wrote:
>
>>> perldoc -f unlink
>>>
>>> Note: "unlink" will not delete directories unless you are superuser and
>>> the -U flag is supplied to Perl.
>>
>>
>> Have you actually done that? Normally, I do go by
perldoc -f unlink
Note: "unlink" will not delete directories unless you are superuser and
the -U flag is supplied to Perl.
Have you actually done that? Normally, I do go by perldoc but in this case,
Yes, that is where I got the info about removing a directpry which is
what you asked about.
for
On 2/28/05 7:15 PM, in article [EMAIL PROTECTED],
"JupiterHost.Net" <[EMAIL PROTECTED]> wrote:
>
>
> Robert wrote:
>> I know the directory where the files I want to delete are stored. I know the
>> files all look like "msqupd.log.somenumber", I have tried a few things to
>> pass the directory to
JupiterHost.Net wrote:
Robert wrote:
I know the directory where the files I want to delete are stored. I
know the
files all look like "msqupd.log.somenumber", I have tried a few things to
pass the directory to unlink without success. The directory does have a
space in it (I am not sure if that ma
Robert wrote:
I know the directory where the files I want to delete are stored. I know the
files all look like "msqupd.log.somenumber", I have tried a few things to
pass the directory to unlink without success. The directory does have a
space in it (I am not sure if that matters).
I have had succe
I know the directory where the files I want to delete are stored. I know the
files all look like "msqupd.log.somenumber", I have tried a few things to
pass the directory to unlink without success. The directory does have a
space in it (I am not sure if that matters).
I have had success with a more
> -Original Message-
> From: Nikola Janceski [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 23, 2002 2:48 PM
> To: 'Jonathan E. Paton'; [EMAIL PROTECTED]
> Subject: RE: silly unlink question..
>
>
> okay so this works:
>
> @files = ;
&
opendir/readdir/closedir to
do this, but I wanted to know why the second example doesn't work.
-Original Message-
From: Jonathan E. Paton [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 23, 2002 2:24 PM
To: [EMAIL PROTECTED]
Subject: Re: silly unlink question..
> But can some
> okay so this works:
>
> @files = ;
> print "@files\n";
>
is obviously not a filehandle, or a
variable containing one. Hence it's a glob.
> but this doesn't:
>
> $search = "/home/*/*.txt";
> @files = <$search>;
> print "@files\n";
>
<$search> is treated as a named filehandle, since that i
> But can someone explain the <*.bak>? how does that work
> and what does it do? (and where is there a description
> of it's use)? Thanx
File glob. Returns an array of filenames which match the
regex /*\.bak$/ - basically those that end in .bak
This is a very Unix like feature of Perl, which
in the man perlfunc page we see:
unlink LIST
unlink Deletes a list of files. Returns the number of
files successfully deleted.
$cnt = unlink 'a', 'b', 'c';
unlink @goners;
unlink <*.bak>;
Note: "unlink" wil
12 matches
Mail list logo
