Bill Landry wrote:
> Dennis Peterson wrote the following on 9/25/2007 9:45 PM -0800:
>> Also - if you do all your tests up front and discover you'll need to run
>> multiple instances of perl you may find you can collect multiple code
>> segments into a single execution of Perl and get everything
Dennis Peterson wrote the following on 9/25/2007 9:45 PM -0800:
> Also - if you do all your tests up front and discover you'll need to run
> multiple instances of perl you may find you can collect multiple code
> segments into a single execution of Perl and get everything in one pass.
> Do as mu
-- Dennis Peterson said the following on 9/25/07 7:00 PM:
> Jan-Pieter Cornet wrote:
>
>> So, TIMTOTDI squared (look ma', no perl!). This does the same as
>> date +%s too:
>>
>> echo|awk '{print systime()}'
>>
>
> But not in Solaris which is where the OP's original hack was born. You
> need
Bill Landry wrote:
> Dennis Peterson wrote the following on 9/25/2007 8:06 PM -0800:
>> Bill Landry wrote:
>>
>>
>>> Okay, let's try this again. A new update has been posted that will first
>>> try
>>> "date +%s" and if that fails, then it will automatically fall back to a perl
>>> option. I
Dennis Peterson wrote the following on 9/25/2007 8:06 PM -0800:
> Bill Landry wrote:
>
>
>> Okay, let's try this again. A new update has been posted that will first try
>> "date +%s" and if that fails, then it will automatically fall back to a perl
>> option. I didn't update the version number
Kyle Lanclos wrote:
> Dennis wrote:
>> You can rip out a lot of code (well, some code) if you just use the Perl
>> date method by default and forget the date +%s stuff entirely.
>
> Your mileage may vary.
>
> $ time perl -le print+time
>
> real0m0.002s
>
> $ time date +%s
>
> real0m0.
Dennis wrote:
> You can rip out a lot of code (well, some code) if you just use the Perl
> date method by default and forget the date +%s stuff entirely.
Your mileage may vary.
$ time perl -le print+time
real0m0.002s
$ time date +%s
real0m0.001s
(Those results were surprisingly consi
Bill Landry wrote:
>
> Okay, let's try this again. A new update has been posted that will first try
> "date +%s" and if that fails, then it will automatically fall back to a perl
> option. I didn't update the version number, just the version info:
You can rip out a lot of code (well, some code
Bill Landry wrote:
> After a discussion on the clamav-users list yesterday of an issue a
> couple of script users were experiencing with write access to the
> temporary directory, I made a change to the script to overcome this
> issue. There are also a couple of other script modifications to make
Jan-Pieter Cornet wrote:
>
> So, TIMTOTDI squared (look ma', no perl!). This does the same as
> date +%s too:
>
> echo|awk '{print systime()}'
>
But not in Solaris which is where the OP's original hack was born. You
need gawk:
echo|gawk '{print systime()}'
My favorite absurd method in S
On Tue, Sep 25, 2007 at 04:17:41PM -0700, Dennis Peterson wrote:
> >>> Epoch time:
> >
> > Golfed:
> >
> > perl -le print+time
>
> It wouldn't be Perl if there were only one way to do it ;)
But it's not necessarily good to include all possible ways. I mean,
this works too:
perl -ple '$_=$^
Jan-Pieter Cornet wrote:
> On Tue, Sep 25, 2007 at 03:17:35PM -0700, Bill Landry wrote:
>>> Epoch time:
>>> perl -e 'print time() . "\n";'
>
> Golfed:
>
> perl -le print+time
>
> You can even leave the -l switch if used in ``, because the trailing
> newline doesn't matter there.
>
It wouldn't
On Tue, Sep 25, 2007 at 03:17:35PM -0700, Bill Landry wrote:
> > Epoch time:
> > perl -e 'print time() . "\n";'
Golfed:
perl -le print+time
You can even leave the -l switch if used in ``, because the trailing
newline doesn't matter there.
--
Jan-Pieter Cornet <[EMAIL PROTECTED]>
!! Disclamer:
Dennis Peterson wrote:
> Bill Landry wrote:
>> Bill Landry wrote:
>>> After a discussion on the clamav-users list yesterday of an issue a
>>> couple of script users were experiencing with write access to the
>>> temporary directory, I made a change to the script to overcome this
>>> issue. There a
Bill Landry wrote:
> Bill Landry wrote:
>> After a discussion on the clamav-users list yesterday of an issue a
>> couple of script users were experiencing with write access to the
>> temporary directory, I made a change to the script to overcome this
>> issue. There are also a couple of other scri
Bill Landry wrote:
> After a discussion on the clamav-users list yesterday of an issue a
> couple of script users were experiencing with write access to the
> temporary directory, I made a change to the script to overcome this
> issue. There are also a couple of other script modifications to make
DBS Labs wrote:
> Rob MacGregor,
>
> I am aware that your crystal ball is broken, because you could not see my
> original post either, which I have included again for your benefit. This was
> my second post because no one responded to my first.
>
You didn't mention where you installed from
Oliver,
Am/On Mon, 24 Sep 2007 13:21:50 +0200 schrieb/wrote Oliver Schwarz:
>look into the config file of clamav. there's an option which lets it
>fix stale sockets.
thanks a lot, that did the trick :-)
Thanks and all the best
Matthias
___
Help us
Rob MacGregor,
I am aware that your crystal ball is broken, because you could not see my
original post either, which I have included again for your benefit. This was
my second post because no one responded to my first.
I just installed ClamAV-0.91.2 on a Redhat EL 4 server for testing. The
19 matches
Mail list logo
