Re: An appropriate directory search tool?

[mick crane]

On 2018-10-21 02:16, John Crawley wrote:

On 20/10/2018 19.28, Richard Owlett wrote:
...I would have expected to use an explicit pipe command between 
'find' and 'grep'.


In fact, depending on the exact conditions of your search, you might
not need to use find at all. 'grep -r' will do a recursive search,
starting at whatever directory you give it, looking inside every file
for some content. Like:

grep -r 'keyword_or_regex' dirname

Of course, 'man grep' for various options...


certainly grep especially if you can't remember where you put something.
If it's just filenames then I like 'locate' as it seems quick once the 
database is updated.

apart from the default look "everywhere" there's

"updatedb -o db_file -U source_directory"

"locate -i -d db_file text_to_look_for"

"-i" ignores case

as an aside there is so much to try to understand about how this stuff 
is organised and all the syntax for bash, perl and the useful provided 
software that you can spend a great deal of time there. Especially if 
you are a little bit elderly perhaps better to be familiar with just the 
things you need to get your project done.


mick






--
Key ID4BFEBB31

Re: perl; Trying to get File::stat to work

[David Christensen]

On 10/19/18 7:47 PM, Martin McCormick wrote:

#!/usr/bin/perl -w
use strict;
use warnings::unused;
use File::stat;
use File::Spec;

my $last_update_time;

$last_update_time = ( stat("testfile") )[9];
printf("%d\n",$last_update_time);


My system:

2018-10-20 20:59:53 dpchrist@vstretch ~/sandbox/perl
$ cat /etc/debian_version
9.5

2018-10-20 21:00:10 dpchrist@vstretch ~/sandbox/perl
$ perl -v

This is perl 5, version 24, subversion 1 (v5.24.1) built for 
x86_64-linux-gnu-thread-multi

(with 81 registered patches, see perl -V for more detail)

Copyright 1987-2017, Larry Wall

Perl may be copied only under the terms of either the Artistic License 
or the

GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.


Create a test file:

2018-10-20 20:59:22 dpchrist@vstretch ~/sandbox/perl
$ touch testfile


Your program:

2018-10-20 20:57:38 dpchrist@vstretch ~/sandbox/perl
$ vi File-stat.pl

#!/usr/bin/perl -w
use strict;
use warnings::unused;
use File::stat;
use File::Spec;

my $last_update_time;

$last_update_time = ( stat("testfile") )[9];
printf("%d\n",$last_update_time);


Compile it:

2018-10-20 21:00:26 dpchrist@vstretch ~/sandbox/perl
$ perl -c File-stat.pl
Can't locate warnings/unused.pm in @INC (you may need to install the 
warnings::unused module) (@INC contains: 
/home/dpchrist/perl5/lib/perl5/5.24.1/x86_64-linux-gnu-thread-multi 
/home/dpchrist/perl5/lib/perl5/5.24.1 
/home/dpchrist/perl5/lib/perl5/x86_64-linux-gnu-thread-multi 
/home/dpchrist/perl5/lib/perl5 /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
File-stat.pl line 3.

BEGIN failed--compilation aborted at File-stat.pl line 3.


The Perl binary is installed in different locations on different 
systems.  Revise shebang line to something that is supposed to be more 
portable.



Leave off '-w' option on shebang line.  'use warnings' normally:


2018-10-20 21:00:57 dpchrist@vstretch ~/sandbox/perl
$ vi File-stat.pl

#!/usr/bin/env perl
use strict;
#use warnings::unused;
use warnings;
use File::stat;
use File::Spec;

my $last_update_time;

$last_update_time = ( stat("testfile") )[9];
printf("%d\n",$last_update_time);


Compile:

2018-10-20 21:01:48 dpchrist@vstretch ~/sandbox/perl
$ perl -c File-stat.pl
File-stat.pl syntax OK


Run:

2018-10-20 21:01:58 dpchrist@vstretch ~/sandbox/perl
$ perl File-stat.pl
Use of uninitialized value $last_update_time in printf at File-stat.pl 
line 11.

0


So, the error is reproducible.


RFTM File::stat.  Note that File::stat overloads Perl's core stat() 
function (becomes File::stat object constructor).  'stat' now returns an 
object, not a list.



Use Data::Dumper to see what's going on.


File::Spec is unused -- comment it out.


Use object-oriented attribute accessor method 'mtime' to obtain file 
modification time.



2018-10-20 21:04:58 dpchrist@vstretch ~/sandbox/perl
$ vi File-stat.pl

#!/usr/bin/env perl
use strict;
#use warnings::unused;
use warnings;
use Data::Dumper;
use File::stat;
#use File::Spec;

# my $last_update_time;

#$last_update_time = ( stat("testfile") )[9];
#printf("%d\n",$last_update_time);

my $f = "testfile";

my $st = stat($f) or die "File::stat constructor failed: $!";
print Data::Dumper->Dump([$st], [qw(st)]);

printf("%d\n", $st->mtime);

2018-10-20 21:16:11 dpchrist@vstretch ~/sandbox/perl
$ perl -c File-stat.pl
File-stat.pl syntax OK

2018-10-20 21:17:22 dpchrist@vstretch ~/sandbox/perl
$ perl File-stat.pl
$st = bless( [
   20,
   970783,
   33188,
   1,
   13250,
   13250,
   0,
   0,
   1540094388,
   1540094388,
   1540094388,
   4096,
   0
 ], 'File::stat' );
1540094388


David

Re: An appropriate directory search tool?

[John Crawley]

On 20/10/2018 19.28, Richard Owlett wrote:
...I would have expected to use an 
explicit pipe command between 'find' and 'grep'.


In fact, depending on the exact conditions of your search, you might not 
need to use find at all. 'grep -r' will do a recursive search, starting 
at whatever directory you give it, looking inside every file for some 
content. Like:


grep -r 'keyword_or_regex' dirname

Of course, 'man grep' for various options...

--
John

Re: An appropriate directory search tool?

[Håkon Alstadheim]

Den 20. okt. 2018 21:05, skrev Brian:
> On Sat 20 Oct 2018 at 07:19:50 -0500, Richard Owlett wrote:
>
>> On 10/20/2018 06:37 AM, Joe wrote:
>>> On Sat, 20 Oct 2018 05:28:52 -0500
>>> Richard Owlett  wrote:
>>>
 On 10/20/2018 04:44 AM, to...@tuxteam.de wrote:
> On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:
>> I think my original post needs a rewrite ;/
>>
>> I'm looking for a directory search tool with specific capabilities
>> which would fit comfortably with my work environment.
> [...]
>> I suspect that what I want would most likely be a command line
>> tool. Perhaps a script will be required. But, before reinventing
>> the wheel, I ask "Does an appropriate command already exist?"
> [...]
>
> Judging by your (second) post, I get the feeling that the answers
> given in this list haven't reached you (at whatever level).
 But they did.
 That's why I wrote 'My take away from answers so far is "A script
 will be required." '
 Perhaps we have different ideas of the definition of "script".
 I saw the examples which worked as scripts (even if written as one
 liners). If I had attempted to use bash, I would have expected to use
 an explicit pipe command between 'find' and 'grep'.

>>> Have you looked at 'zenity' for (somewhat) graphicising scripts? Not
>>> quite the full GUI experience, but quick and dirty.
>>>
>>> https://www.linuxjournal.com/content/make-your-scripts-user-friendly-zenity
>>>
>> Had never heard of 'zenity'.
>> I browsed the text of the page. To read it as intended I'll have to use an
>> alternate profile -- it expects "features" I've explicitly disabled.
>>
>> I searched for 'zenity tutorials'. The first few I found encourage further
>> investigation.
> I'd stay awy from zenity if I were you. The same advice applies to yad.
> As for dialog - don't go near it. You will be a lot happier.
>
If you want some interacivity-support for your find, emacs (and most
other coding-editors I suppose) can run find and let you pick through
the results in an editing-buffer. In emacs it is M-x find-dired, which
lets you pick the directory under which to search, hit enter, and then
enter the search criteria for find, and hit enter. If you want grep with
that, you do M-x find-grep-dired, and input directory and search-string
to look for INSIDE the files found. When you hit enter after the
criteria, it will show the results in a buffer, an you can hit enter on
any of the results to open that file.

Re: An appropriate directory search tool?

[Brian]

On Sat 20 Oct 2018 at 07:19:50 -0500, Richard Owlett wrote:

> On 10/20/2018 06:37 AM, Joe wrote:
> > On Sat, 20 Oct 2018 05:28:52 -0500
> > Richard Owlett  wrote:
> > 
> > > On 10/20/2018 04:44 AM, to...@tuxteam.de wrote:
> > > > On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:
> > > > > I think my original post needs a rewrite ;/
> > > > > 
> > > > > I'm looking for a directory search tool with specific capabilities
> > > > > which would fit comfortably with my work environment.
> > > > 
> > > > [...]
> > > > > I suspect that what I want would most likely be a command line
> > > > > tool. Perhaps a script will be required. But, before reinventing
> > > > > the wheel, I ask "Does an appropriate command already exist?"
> > > > 
> > > > [...]
> > > > 
> > > > Judging by your (second) post, I get the feeling that the answers
> > > > given in this list haven't reached you (at whatever level).
> > > 
> > > But they did.
> > > That's why I wrote 'My take away from answers so far is "A script
> > > will be required." '
> > > Perhaps we have different ideas of the definition of "script".
> > > I saw the examples which worked as scripts (even if written as one
> > > liners). If I had attempted to use bash, I would have expected to use
> > > an explicit pipe command between 'find' and 'grep'.
> > > 
> > 
> > Have you looked at 'zenity' for (somewhat) graphicising scripts? Not
> > quite the full GUI experience, but quick and dirty.
> > 
> > https://www.linuxjournal.com/content/make-your-scripts-user-friendly-zenity
> > 
> 
> Had never heard of 'zenity'.
> I browsed the text of the page. To read it as intended I'll have to use an
> alternate profile -- it expects "features" I've explicitly disabled.
> 
> I searched for 'zenity tutorials'. The first few I found encourage further
> investigation.

I'd stay awy from zenity if I were you. The same advice applies to yad.
As for dialog - don't go near it. You will be a lot happier.

-- 
Brian.

Re: Impossible to migrate to buster

[Cindy-Sue Causey]

On 10/20/18, Pierre Couderc  wrote:
> I have updated my sources.list from stretch :
>
> root@server:~# cat  /etc/apt/sources.list
>
> deb http://debian.proxad.net/debian/ buster main contrib
> deb-src http://debian.proxad.net/debian/ buster main contrib
>
> deb http://security.debian.org buster/updates main contrib
> deb-src http://security.debian.org buster/updates main contrib
>
> # buster-updates, previously known as 'volatile'
> deb http://debian.proxad.net/debian/ buster-updates main contrib
> deb-src http://debian.proxad.net/debian/ buster-updates main contrib
> root@server:~#apt update
>
> root@server:~# apt update
> Hit:1 http://debian.proxad.net/debian buster InRelease
> Hit:2 http://security.debian.org buster/updates InRelease
> Hit:3 http://debian.proxad.net/debian buster-updates InRelease
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 295 packages can be upgraded. Run 'apt list --upgradable' to see them.


I saw that this thread was already solved. Congratulations! I just
wanted to highlight that last line there and thank the Developer(s)
who added it to apt. It's a handy, useful tip popping up in a very
appropriate place that makes it accessible to users of various
experience levels. I'm always hopeful that tips like that inspire new
users to follow their curiosity over to "man apt" to see what other
helpful flags/commands might be humbly lurking in the nearby shadows.


> Do you want to continue? [Y/n] Abort.
> root@server:~#
>
> The upgrade is aborted without I have keyed anything !!!
>
> What am I missing ?


I don't know if that part was considered also solved so am a-suming
most likely yes. Just throwing in that there's always the possibility
of a stuck keyboard key if nothing else works in that specific kind of
case.

Stuck keyboard keys are the first thing I test. I do so by giving my
Ctrl, Alt, and Shift keys (all *6* of them if present) a couple pops.
Doesn't always help, but it *has* helped enough that it's a conscious
check point on my own debugging list. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Impossible to migrate to buster

[Brian]

On Sat 20 Oct 2018 at 16:09:07 +0200, Pierre Couderc wrote:

> 
> On 10/20/18 10:02 AM, Pierre Couderc wrote:
> > .
> > Need to get 182 MB of archives.
> > After this operation, 417 MB of additional disk space will be used.
> > Do you want to continue? [Y/n] Abort.
> > root@server:~#
> > 
> > The upgrade is aborted without I have keyed anything !!!
> > 
> > What am I missing ?
> > 
> > Thanks
> > 
> > PC
> > 
> Thnk you for all your answers.
> 
> I have not found this option -y in apt, but it works and buster is
> installed!

The apt manual says:

 > Much like apt itself, its manpage is intended as an end user
 > interface and as such only mentions the most used commands
 > and options partly to not duplicate information in multiple
 > places and partly to avoid overwhelming readers with a
 > cornucopia of options and details.

so, to some extent, this is a justification for the -y option not being
documented. dist-upgrade is not documented either. 

> apt dist-upgrade and apt autoremove  have the same problem worked aroun by
> -y option.
> 
> Anyway,  have found that the problem occurs only in a ssh session not
> directly on the local console !!
> 
> I do not understand why ?

Neither does anyone else, I think. You could think in terms of its being
a bug and reporting it.

-- 
Brian.

pppd incomatible with libradcli4

[Eugene M. Zheganin]

Hello,

I'm trying to set up the VPN stack using xl2tpd/strongswan on recent 
Debian 9.5, and so far everything is working except radius 
authentication (I have a freeradius3 setup which is fully working, so I 
need to use it to authenticate users). Seems like pppd is totally 
incompatible with libradcli4: when I add


plugin radius.so
plugin radattr.so

into  the /etc/ppp/options.xl2tpd configuration file, pppd starts 
complaining about missing directives:


first, /etc/radiusclient/radiusclient.conf cannot be read. Okay, I don't 
know if it's right, but since radiusclient1 seems to be vanished 
completely, I can link /etc/radcli as /etc/radiusclient.


Then the following happens:


/etc/radiusclient/radiusclient.conf: mapfile not specified

 /etc/radiusclient/radiusclient.conf: seqfile not specified


These two can be easily (again, not sure if it' s the right way to fix 
it) by specifying the old seqfile/mapfile directives, but then I'm stuck at



rc_read_dictionary: invalid type on line 34 of dictionary 
/etc/radcli/dictionary



Seems like pppd and libradcli4 have totally different ideas about radius 
dictionnaries. How do you guys handle it ?



Thanks.

Eugene.

Re: Impossible to migrate to buster

[Pierre Couderc]

On 10/20/18 10:02 AM, Pierre Couderc wrote:

.
Need to get 182 MB of archives.
After this operation, 417 MB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.
root@server:~#

The upgrade is aborted without I have keyed anything !!!

What am I missing ?

Thanks

PC


Thnk you for all your answers.

I have not found this option -y in apt, but it works and buster is 
installed!


apt dist-upgrade and apt autoremove  have the same problem worked aroun 
by -y option.



Anyway,  have found that the problem occurs only in a ssh session not 
directly on the local console !!


I do not understand why ?

Re: An appropriate directory search tool?

[rhkramer]

On Saturday, October 20, 2018 08:35:51 AM Richard Owlett wrote:
> I don't think "find" itself is the problem.
> Debian seems to do some 'black magic' to conflate "standard output" and
> "standard input". Otherwise a pipe command would be required between
> "find" and "grep".

I didn't go back all the way in the thread to look for a command without a 
pipe between find and grep, but, the line I did find using both find and grep 
used -exec as that black magic.

Re: An appropriate directory search tool?

[rhkramer]

On Friday, October 19, 2018 11:29:13 AM Greg Wooledge wrote:
> There's also .

I'm not the OP, but I wanted to say that I find the pages on your wiki (at 
least the ones I've looked at) to be helpful and well-written.

Re: An appropriate directory search tool?

[Dan Purgert]

Richard Owlett wrote:
> On 10/20/2018 05:23 AM, Étienne Mollier wrote:
>> [snip]
>>> My take away from answers so far is "A script will be required."
>> 
>> Not necessarily, the trouble is: "find" is so vast, you can
>> spend hours in the manual to search for adequate option for
>> your specific need, and end up writing a script, instead of
>> having found "the proper option".
>
> I don't think "find" itself is the problem.
> Debian seems to do some 'black magic' to conflate "standard output" and 
> "standard input". Otherwise a pipe command would be required between 
> "find" and "grep".

No it doesn't. find has functionality built in to pass results onward
(-exec or -xargs)


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: Impossible to migrate to buster

[Hans]

Am Samstag, 20. Oktober 2018, 14:37:58 CEST schrieb Norbert Brondeau:
Hi, 

just an idea: apt is calling either apt-get or aptitude, whatever it thinks is 
the best option. I believe, in this case it is calling aptitude, what is not 
the best choice for a full distribution upgrade.

I suggest, to run 

apt-get update

then 

apt-get dist-upgrade

If this works, run 

aptitude full-upgrade

When your system is fully upgrade, you can do all the upgrades with apt again.


Hope this helps!

Good luck and all the best

Hans 
> Just try
> 
> apt dist-upgrade
> 
> Le sam. 20 oct. 2018 à 10:42, Brian  a écrit :

Re: Impossible to migrate to buster

[Norbert Brondeau]

Just try

apt dist-upgrade
Le sam. 20 oct. 2018 à 10:42, Brian  a écrit :
>
> On Sat 20 Oct 2018 at 10:02:40 +0200, Pierre Couderc wrote:
>
> [...]
>
> > root@server:~# apt upgrade
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Calculating upgrade... Done
>
> [...]
>
> > 295 upgraded, 61 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 182 MB of archives.
> > After this operation, 417 MB of additional disk space will be used.
> > Do you want to continue? [Y/n] Abort.
> > root@server:~#
> >
> > The upgrade is aborted without I have keyed anything !!!
> >
> > What am I missing ?
>
> I've really no idea what is going on here, but try
>
> apt -y upgrade.
>
> --
> Brian.
>

Re: firefox palemoon waterfox baselisk problem, not on chromium

[Andrew McGlashan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

On 20/10/18 11:16, arne wrote:
> While browsing on stock updated Debian stretch I get several times
> a day:
> 
> Secure Connection Failed
> 
> The connection to www.google.com was interrupted while the page was
> loading.
> 
> The page you are trying to view cannot be shown because the 
> authenticity of the received data could not be verified.

Maybe OCSP ?

Google doesn't seem to care for OCSP, so that could be a problem.

If you enforce OCSP to fail if it can't get an answer, then you will
likely see problems with Google sites ... regularly.  Other sites
aren't so uncaring about OCSP as Google whom think they own the online
world.

Google imposes all sorts of things for *their* own greater good,
thinking they know best all the time; it can be very frustrating and I
wish they would butt out.  Consequently, the chances of me using
Chrome or related browsers is quite low and I would definitely not use
them for my default, ever.

I do use Pale Moon, don't know exactly what the connection is with
"basilisk-browser" (other thread).  I also use Firefox and Tor Browser
Bundle.  On the whole, I am fairly happy with Pale Moon.  Firefox,
partly driven by Google's Chrome, also make decisions that I'm not
happy with, hence the use of Pale Moon predominantly.


Cheers
A.
-BEGIN PGP SIGNATURE-

iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCW8shTgAKCRCoFmvLt+/i
+9IXAP4vx1FYwxEBl80PjD7IRp6fC5TfMBLtzz0f8hh31TrNegEA3n23t7ZrZv6X
3D93I7jQFFCIt55ffOff6yqGLgXbGdo=
=8geS
-END PGP SIGNATURE-

Re: An appropriate directory search tool?

[Richard Owlett]

On 10/20/2018 05:23 AM, Étienne Mollier wrote:

[snip]

My take away from answers so far is "A script will be required."


Not necessarily, the trouble is: "find" is so vast, you can
spend hours in the manual to search for adequate option for
your specific need, and end up writing a script, instead of
having found "the proper option".


I don't think "find" itself is the problem.
Debian seems to do some 'black magic' to conflate "standard output" and 
"standard input". Otherwise a pipe command would be required between 
"find" and "grep".

Re: An appropriate directory search tool?

[Richard Owlett]

On 10/20/2018 06:24 AM, Joe wrote:

On Sat, 20 Oct 2018 11:44:37 +0200
 wrote:


On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:

I think my original post needs a rewrite ;/

I'm looking for a directory search tool with specific capabilities
which would fit comfortably with my work environment.


[...]


I suspect that what I want would most likely be a command line tool.
Perhaps a script will be required. But, before reinventing the
wheel, I ask "Does an appropriate command already exist?"


[...]

Judging by your (second) post, I get the feeling that the answers
given in this list haven't reached you (at whatever level). Most
of them were quite positive: "yes, such a tool exists, it's called
'find'", some of them even implemented a sketch of a solution to
your concrete example.

Since you don't even try to make reference to *any* of the numerous
proposals flung around here, I'm at a loss on how to help you.

For now, I'll just give up, sorry.


I took it to mean that he wants a GUI tool.



No.
I date from days of 026, KSR-35, VT 100 , S100 and CPM-80.
Many years spent with M$ Windows --> gui user.
If a GUI does the task, good.
However flexibility frequently requires working with command line.

Re: Impossible to migrate to buster

[Norbert Brondeau]

A 09:26 20/10/18, Brian a écrit :
>On Sat 20 Oct 2018 at 10:02:40 +0200, Pierre Couderc wrote:
>
>[...]
>
>> root@server:~# apt upgrade
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Calculating upgrade... Done
>
>[...]
>
>> 295 upgraded, 61 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 182 MB of archives.
>> After this operation, 417 MB of additional disk space will be used.
>> Do you want to continue? [Y/n] Abort.
>> root@server:~#
>>
>> The upgrade is aborted without I have keyed anything !!!
>>
>> What am I missing ?
>
>I've really no idea what is going on here, but try
>
>apt -y upgrade.
>

apt dist-upgrade

Re: perl; Trying to get File::stat to work

[Martin McCormick]

Bob McGowan  writes:
> It looks like this has to do with mixing the usage of the "native" stat of
> Perl with the "object" version from File::stat.
> 
> 
> 
> The 'stat' from File::stat returns a reference to an object, which has the
> stuff you're wanting, tucked away internally as object variables.  You 
> need
> to do:
> 
> 
> use File::stat;
> 
> $statRef = stat('testfile');
> 
> $mtime = $statRef->mtime ()
> 
> Hoping this helps.
> 
> Bob

Thank you and thanks to Dave Sherohman   He
wrote:

> Your actual question has already been answered, but, for future
> reference, PerlMonks (https://www.perlmonks.org/) is still around and
> there are also several Perl folks who frequent StackOverflow
> (https://stackoverflow.com/), so you can generally get good answers to
> Perl questions pretty quickly from either of those sites.

It worked perfectly plus I now much better understand how
the pieces all fit together.

Martin

Re: An appropriate directory search tool?

[Richard Owlett]

On 10/20/2018 06:37 AM, Joe wrote:

On Sat, 20 Oct 2018 05:28:52 -0500
Richard Owlett  wrote:


On 10/20/2018 04:44 AM, to...@tuxteam.de wrote:

On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:

I think my original post needs a rewrite ;/

I'm looking for a directory search tool with specific capabilities
which would fit comfortably with my work environment.


[...]
   

I suspect that what I want would most likely be a command line
tool. Perhaps a script will be required. But, before reinventing
the wheel, I ask "Does an appropriate command already exist?"


[...]

Judging by your (second) post, I get the feeling that the answers
given in this list haven't reached you (at whatever level).


But they did.
That's why I wrote 'My take away from answers so far is "A script
will be required." '
Perhaps we have different ideas of the definition of "script".
I saw the examples which worked as scripts (even if written as one
liners). If I had attempted to use bash, I would have expected to use
an explicit pipe command between 'find' and 'grep'.



Have you looked at 'zenity' for (somewhat) graphicising scripts? Not
quite the full GUI experience, but quick and dirty.

https://www.linuxjournal.com/content/make-your-scripts-user-friendly-zenity



Had never heard of 'zenity'.
I browsed the text of the page. To read it as intended I'll have to use 
an alternate profile -- it expects "features" I've explicitly disabled.


I searched for 'zenity tutorials'. The first few I found encourage 
further investigation.

Re: An appropriate directory search tool?

[Roberto C . Sánchez]

On Sat, Oct 20, 2018 at 05:28:52AM -0500, Richard Owlett wrote:
> 
> But they did.
> That's why I wrote 'My take away from answers so far is "A script will be
> required." '
> Perhaps we have different ideas of the definition of "script".
> I saw the examples which worked as scripts (even if written as one liners).
> If I had attempted to use bash, I would have expected to use an explicit
> pipe command between 'find' and 'grep'.
> 
While you can certainly do that, the authors find were clearly aware
that the "find one or more files based on some criteria and then perform
one or more operations on those files" would be a common enough workflow
that they included the -exec and -execdir options to find.  With those
you do not need a pipe between find and grep.  It also effectively deals
with the situation where the file list is so long that you exceed the
system limit for the length of a command line.  The -exec option will
perform the specified action once per file found that meets the
criteria, where the pipe approach would pass the entire output of find
into the grep command.  That is sometimes not what you want.

However, if you still want to use the pipe approach, I would advise you
to look at the -print0 option to find and the -0 option to xargs.  Since
the normal find output is one file name per line and since newlines are
valid in file names, it may sometimes not yield the expected result.  A
NULL character, however, is not valid in a filename, so it is an
effective separator and you can use it like this:

find   -print0 | xargs -0  

That will ensure that you actually get the result you expect and as a
bonus xargs handles the "do this command once for each input line"
dance, so you are not likely to exceed the system limit on the length of
a command line.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: basilisk-browser

[Roberto C . Sánchez]

On Fri, Oct 19, 2018 at 11:30:05PM -0300, fmn...@fmneto.com.br wrote:
> On 2018-10-19 23:19, Ben Finney wrote:
> > Dominik George  writes:
> > 
> > > >> > [1] https://github.com/jasperla/openbsd-wip/issues/86
> > > 
> > > Seriously? They forbid linking against libraries if their code is not
> > > shipped with their sources?
> > 
> > They don't forbid that.
> > 
> > What they forbid is redistributing the modified work with the Pale Moon
> > branding.
> 
>Honestly they can do whatever they want. What's really obnoxious is to
> open a ticket on somebody else's git and *start* it by saying "You WILL do
> this and that", without even trying to establish some kind of dialogue.
> 
It is, however, an excellent lesson for teaching those who choose
software development as a vocation/career based on not having to deal
with people very much.  I frequently point out to my students that
programmers require "people skills" just as much as any other
profession.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: An appropriate directory search tool?

[Joe]

On Sat, 20 Oct 2018 05:28:52 -0500
Richard Owlett  wrote:

> On 10/20/2018 04:44 AM, to...@tuxteam.de wrote:
> > On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:  
> >> I think my original post needs a rewrite ;/
> >>
> >> I'm looking for a directory search tool with specific capabilities
> >> which would fit comfortably with my work environment.  
> > 
> > [...]
> >   
> >> I suspect that what I want would most likely be a command line
> >> tool. Perhaps a script will be required. But, before reinventing
> >> the wheel, I ask "Does an appropriate command already exist?"  
> > 
> > [...]
> > 
> > Judging by your (second) post, I get the feeling that the answers
> > given in this list haven't reached you (at whatever level).  
> 
> But they did.
> That's why I wrote 'My take away from answers so far is "A script
> will be required." '
> Perhaps we have different ideas of the definition of "script".
> I saw the examples which worked as scripts (even if written as one 
> liners). If I had attempted to use bash, I would have expected to use
> an explicit pipe command between 'find' and 'grep'.
> 

Have you looked at 'zenity' for (somewhat) graphicising scripts? Not
quite the full GUI experience, but quick and dirty.

https://www.linuxjournal.com/content/make-your-scripts-user-friendly-zenity
-- 
Joe

Re: An appropriate directory search tool?

[Joe]

On Sat, 20 Oct 2018 11:44:37 +0200
 wrote:

> On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:
> > I think my original post needs a rewrite ;/
> > 
> > I'm looking for a directory search tool with specific capabilities
> > which would fit comfortably with my work environment.  
> 
> [...]
> 
> > I suspect that what I want would most likely be a command line tool.
> > Perhaps a script will be required. But, before reinventing the
> > wheel, I ask "Does an appropriate command already exist?"  
> 
> [...]
> 
> Judging by your (second) post, I get the feeling that the answers
> given in this list haven't reached you (at whatever level). Most
> of them were quite positive: "yes, such a tool exists, it's called
> 'find'", some of them even implemented a sketch of a solution to
> your concrete example.
> 
> Since you don't even try to make reference to *any* of the numerous
> proposals flung around here, I'm at a loss on how to help you.
> 
> For now, I'll just give up, sorry.

I took it to mean that he wants a GUI tool.

-- 
Joe

Re: An appropriate directory search tool?

[Richard Owlett]

On 10/20/2018 04:44 AM, to...@tuxteam.de wrote:

On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:

I think my original post needs a rewrite ;/

I'm looking for a directory search tool with specific capabilities
which would fit comfortably with my work environment.


[...]


I suspect that what I want would most likely be a command line tool.
Perhaps a script will be required. But, before reinventing the
wheel, I ask "Does an appropriate command already exist?"


[...]

Judging by your (second) post, I get the feeling that the answers
given in this list haven't reached you (at whatever level).


But they did.
That's why I wrote 'My take away from answers so far is "A script will 
be required." '

Perhaps we have different ideas of the definition of "script".
I saw the examples which worked as scripts (even if written as one 
liners). If I had attempted to use bash, I would have expected to use an 
explicit pipe command between 'find' and 'grep'.




Most
of them were quite positive: "yes, such a tool exists, it's called
'find'", some of them even implemented a sketch of a solution to
your concrete example.

Since you don't even try to make reference to *any* of the numerous
proposals flung around here, I'm at a loss on how to help you.

For now, I'll just give up, sorry.

Cheers
-- tomás

Re: An appropriate directory search tool?

[Étienne Mollier]

Good Day,

On 10/20/18 11:32 AM, Richard Owlett wrote:
> I think my original post needs a rewrite ;/

Well, let's stick to the text then...

> I'm looking for a directory search tool with specific capabilities which 
> would fit comfortably with my work environment.
> 
> The "MATE Search Tool" comes close.
> It can:
>   Select a starting directory.

$ find doc/

>   Search for a specific extension.

$ find -iname '*.tex'

>   Search for a keyword in file content.

$ find -exec grep -Eq "\" '{}' \; -print

> It cannot:
>    Search ONLY the specified directory.

$ find -maxdepth 1

>    Return files that DO NOT contain a keyword.

$ find -not -exec grep -Eq "\" '{}' \; -print

Putting it all together, that would give that sort of command:

$ find doc/ \
>   -maxdepth 1 \
>   -iname "*.tex" \
>   -not -exec grep -Eq "\" '{}' \; \
>   -print

The order of search options is important, as each one refines
a bit more the search field among the files.

> "ls" can search by extension and stay in specified directory but not
> include/exclude keywords.

"ls" is good for listing directory content.  "find" is designed
to find files on their inode information (name, last modification
date, size, that kind of stuff).  As soon as you need to deal
with text inside that file, you also need to include execution
of commands designed to read the file and return or not in error
depending on the presence of keywords: "grep" is such a command.

> I suspect that what I want would most likely be a command line too> Perhaps a 
> script will be required. But, before reinventing the wheel, I ask "Does an 
> appropriate command already exist?"

Yes, "find" as command line, will do the job.

> [My immediate problem involves only a couple dozen files so a manual search 
> is feasible.]
> 
> My take away from answers so far is "A script will be required."

Not necessarily, the trouble is: "find" is so vast, you can
spend hours in the manual to search for adequate option for
your specific need, and end up writing a script, instead of
having found "the proper option".

> As I am exploring Tcl/Tk and this tool would provide input to a current Tcl 
> project, I will use it rather than bash.

Note that at no moment Bash has been mentioned.  You could
have launched all these "find" instances from an exec() call
in whatever language you with to use.  :-)

> Thank you.

Kind Regards,
-- 
Étienne Mollier 

Re: An appropriate directory search tool?

[tomas]

On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote:
> I think my original post needs a rewrite ;/
> 
> I'm looking for a directory search tool with specific capabilities
> which would fit comfortably with my work environment.

[...]

> I suspect that what I want would most likely be a command line tool.
> Perhaps a script will be required. But, before reinventing the
> wheel, I ask "Does an appropriate command already exist?"

[...]

Judging by your (second) post, I get the feeling that the answers
given in this list haven't reached you (at whatever level). Most
of them were quite positive: "yes, such a tool exists, it's called
'find'", some of them even implemented a sketch of a solution to
your concrete example.

Since you don't even try to make reference to *any* of the numerous
proposals flung around here, I'm at a loss on how to help you.

For now, I'll just give up, sorry.

Cheers
-- tomás


signature.asc
Description: Digital signature

Re: Impossible to migrate to buster

[Michael Wagner]

On Oct 20, 2018 at 09:26:14, Brian wrote:
> On Sat 20 Oct 2018 at 10:02:40 +0200, Pierre Couderc wrote:
> 
> [...]
> 
> > root@server:~# apt upgrade
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Calculating upgrade... Done
> 
> [...]
> 
> > 295 upgraded, 61 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 182 MB of archives.
> > After this operation, 417 MB of additional disk space will be used.
> > Do you want to continue? [Y/n] Abort.
> > root@server:~#
> > 
> > The upgrade is aborted without I have keyed anything !!!
> > 
> > What am I missing ?
> 
> I've really no idea what is going on here, but try
> 
> apt -y upgrade.

I would first upgrade apt and dpkg.

$apt install apt dpkg

Just my 2¢
Michael

-- 
Spock, you are such a putz!


signature.asc
Description: PGP signature

Re: An appropriate directory search tool?

[Richard Owlett]

I think my original post needs a rewrite ;/

I'm looking for a directory search tool with specific capabilities which 
would fit comfortably with my work environment.


The "MATE Search Tool" comes close.
It can:
  Select a starting directory.
  Search for a specific extension.
  Search for a keyword in file content.
It cannot:
   Search ONLY the specified directory.
   Return files that DO NOT contain a keyword.

"ls" can search by extension and stay in specified directory but not
include/exclude keywords.

I suspect that what I want would most likely be a command line tool.
Perhaps a script will be required. But, before reinventing the wheel, I 
ask "Does an appropriate command already exist?"
[My immediate problem involves only a couple dozen files so a manual 
search is feasible.]


My take away from answers so far is "A script will be required."
As I am exploring Tcl/Tk and this tool would provide input to a current 
Tcl project, I will use it rather than bash.


Thank you.

Re: Impossible to migrate to buster

[Brian]

On Sat 20 Oct 2018 at 11:45:29 +0300, Reco wrote:

>   Hi.
> 
> On Sat, Oct 20, 2018 at 09:26:14AM +0100, Brian wrote:
> > On Sat 20 Oct 2018 at 10:02:40 +0200, Pierre Couderc wrote:
> > 
> > [...]
> > 
> > > root@server:~# apt upgrade
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > Calculating upgrade... Done
> > 
> > [...]
> > 
> > > 295 upgraded, 61 newly installed, 0 to remove and 0 not upgraded.
> > > Need to get 182 MB of archives.
> > > After this operation, 417 MB of additional disk space will be used.
> > > Do you want to continue? [Y/n] Abort.
> > > root@server:~#
> > > 
> > > The upgrade is aborted without I have keyed anything !!!
> > > 
> > > What am I missing ?
> > 
> > I've really no idea what is going on here, but try
> > 
> > apt -y upgrade.
> 
> And then apt runs debconf, and debconf receives whatever keypress that
> was interrupting apt. Sounds risky to me.
> 
> I'd try running apt from iLO/BMC/ILOM.

I suppose 'apt install ' (repeated) might do it.

-- 
Brian.

Re: Impossible to migrate to buster

[Reco]

Hi.

On Sat, Oct 20, 2018 at 09:26:14AM +0100, Brian wrote:
> On Sat 20 Oct 2018 at 10:02:40 +0200, Pierre Couderc wrote:
> 
> [...]
> 
> > root@server:~# apt upgrade
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Calculating upgrade... Done
> 
> [...]
> 
> > 295 upgraded, 61 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 182 MB of archives.
> > After this operation, 417 MB of additional disk space will be used.
> > Do you want to continue? [Y/n] Abort.
> > root@server:~#
> > 
> > The upgrade is aborted without I have keyed anything !!!
> > 
> > What am I missing ?
> 
> I've really no idea what is going on here, but try
> 
> apt -y upgrade.

And then apt runs debconf, and debconf receives whatever keypress that
was interrupting apt. Sounds risky to me.

I'd try running apt from iLO/BMC/ILOM.

Reco

Re: Impossible to migrate to buster

[Brian]

On Sat 20 Oct 2018 at 10:02:40 +0200, Pierre Couderc wrote:

[...]

> root@server:~# apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done

[...]

> 295 upgraded, 61 newly installed, 0 to remove and 0 not upgraded.
> Need to get 182 MB of archives.
> After this operation, 417 MB of additional disk space will be used.
> Do you want to continue? [Y/n] Abort.
> root@server:~#
> 
> The upgrade is aborted without I have keyed anything !!!
> 
> What am I missing ?

I've really no idea what is going on here, but try

apt -y upgrade.

-- 
Brian.

Re: Impossible to migrate to buster

[Norbert Brondeau]

A 10:02 20/10/18, Pierre Couderc a écrit :
>I have updated my sources.list from stretch :
>
>root@server:~# cat  /etc/apt/sources.list
>
>deb http://debian.proxad.net/debian/ buster main contrib
>deb-src http://debian.proxad.net/debian/ buster main contrib
>
>deb http://security.debian.org buster/updates main contrib
>deb-src http://security.debian.org buster/updates main contrib
>
># buster-updates, previously known as 'volatile'
>deb http://debian.proxad.net/debian/ buster-updates main contrib
>deb-src http://debian.proxad.net/debian/ buster-updates main contrib
>root@server:~#apt update
>
>root@server:~# apt update


__ apt dist-upgrade __

have a nice day!

Re: perl; Trying to get File::stat to work

[Dave Sherohman]

On Fri, Oct 19, 2018 at 09:47:11PM -0500, Martin McCormick wrote:
> I am a member of a perl discussion list but it seems to have gone
> away

Your actual question has already been answered, but, for future
reference, PerlMonks (https://www.perlmonks.org/) is still around and
there are also several Perl folks who frequent StackOverflow
(https://stackoverflow.com/), so you can generally get good answers to
Perl questions pretty quickly from either of those sites.

-- 
Dave Sherohman

Impossible to migrate to buster

[Pierre Couderc]

I have updated my sources.list from stretch :

root@server:~# cat  /etc/apt/sources.list

deb http://debian.proxad.net/debian/ buster main contrib
deb-src http://debian.proxad.net/debian/ buster main contrib

deb http://security.debian.org buster/updates main contrib
deb-src http://security.debian.org buster/updates main contrib

# buster-updates, previously known as 'volatile'
deb http://debian.proxad.net/debian/ buster-updates main contrib
deb-src http://debian.proxad.net/debian/ buster-updates main contrib
root@server:~#apt update

root@server:~# apt update
Hit:1 http://debian.proxad.net/debian buster InRelease
Hit:2 http://security.debian.org buster/updates InRelease
Hit:3 http://debian.proxad.net/debian buster-updates InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
295 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@server:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer 
required:
  dh-python libbind9-140 libdns162 libgmime-2.6-0 libicu57 libisc160 
libisccc140 libisccfg140 liblwres141 libnotmuch4 libperl5.24
  libpython3.5-minimal libpython3.5-stdlib libtalloc2 python3-distutils 
python3-lib2to3 python3.5 python3.5-minimal rename sgml-base

  tcpd xml-core
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  apparmor dirmngr e2fsprogs-l10n fdisk gcc-8-base gnupg-l10n 
gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm
  grub-efi-amd64-signed libargon2-1 libbind9-160 libcap2-bin 
libcom-err2 libcryptsetup12 libdns-export1102 libdns1102 libext2fs2
  libfstrm0 libgdbm-compat4 libgdbm6 libgpg-error-l10n libgraphite2-3 
libharfbuzz0b libicu-le-hb0 libicu60 libisc-export169
  libisc169 libisccc160 libisccfg160 libjson-c3 liblmdb0 liblwres160 
libncurses6 libncursesw6 libnss-systemd libpam-cap libperl5.26
  libprocps7 libprotobuf-c1 libpython2-stdlib libpython3.6-minimal 
libpython3.6-stdlib libtinfo6 libunistring2 libzstd1
  linux-image-4.18.0-2-amd64 perl-modules-5.26 python2 python2-minimal 
python3-certifi python3-debconf python3-distutils

  python3-idna python3-lib2to3 python3.6 python3.6-minimal
The following packages will be upgraded:
  adduser apt apt-listchanges apt-utils base-files base-passwd bash 
bash-completion bind9-host bridge-utils bsdmainutils bsdutils
  btrfs-progs busybox bzip2 ca-certificates console-setup 
console-setup-linux coreutils cpio cron dash dbus debconf debconf-i18n
  debian-archive-keyring debianutils dh-python dictionaries-common 
diffutils discover distro-info-data dmidecode dmsetup dpkg
  e2fslibs e2fsprogs efibootmgr emacsen-common file findutils 
gcc-6-base geoip-database gettext-base gnupg gnupg-agent gpgv grep
  groff-base grub-common grub-efi-amd64 grub-efi-amd64-bin grub2-common 
gzip hdparm hostname iamerican ibritish ienglish-common
  ifupdown init init-system-helpers initramfs-tools 
initramfs-tools-core installation-report iproute2 iptables iputils-ping
  irqbalance isc-dhcp-client isc-dhcp-common iso-codes ispell kbd 
keyboard-configuration klibc-utils kmod krb5-locales laptop-detect
  less libapparmor1 libapt-inst2.0 libapt-pkg5.0 libassuan0 
libaudit-common libaudit1 libblkid1 libbsd0 libbz2-1.0 libc-bin
  libc-l10n libc6 libcap-ng0 libcap2 libclass-isa-perl libcomerr2 
libcurl3-gnutls libdb5.3 libdbus-1-3 libdebconfclient0
  libdevmapper1.02.1 libdiscover2 libedit2 libefiboot1 libefivar1 
libelf1 libestr0 libexpat1 libfastjson4 libfdisk1 libffi6
  libfreetype6 libfuse2 libgcc1 libgcrypt20 libgeoip1 libglib2.0-0 
libglib2.0-data libgmime-2.6-0 libgmp10 libgnutls-openssl27
  libgnutls30 libgpg-error0 libgpgme11 libgpm2 libgssapi-krb5-2 
libhogweed4 libidn11 libidn2-0 libip4tc0 libip6tc0 libiptc0
  libk5crypto3 libkeyutils1 libklibc libkmod2 libkrb5-3 libkrb5support0 
libldap-2.4-2 libldap-common liblocale-gettext-perl
  liblockfile-bin liblogging-stdlog0 liblognorm5 liblz4-1 liblzma5 
liblzo2-2 libmagic-mgc libmagic1 libmount1 libmpdec2 libncurses5
  libncursesw5 libnetfilter-conntrack3 libnettle6 libnewt0.52 
libnfnetlink0 libnghttp2-14 libnpth0 libnuma1 libp11-kit0
  libpam-modules libpam-modules-bin libpam-runtime libpam-systemd 
libpam0g libpcre3 libpipeline1 libpng16-16 libpopt0 libpsl5
  libpython-stdlib libpython2.7-minimal libpython2.7-stdlib 
libpython3-stdlib libreadline7 librtmp1 libsasl2-2 libsasl2-modules
  libsasl2-modules-db libseccomp2 libselinux1 libsemanage-common 
libsemanage1 libsepol1 libslang2 libsmartcols1 libsqlite3-0 libss2
  libssh2-1 libssl1.0.2 libssl1.1 libstdc++6 libsystemd0 libtalloc2 
libtasn1-6 libtext-charwidth-perl libtext-iconv-perl libtinfo5
  libtokyocabinet9 libudev1 libusb-0.1-4 libusb-1.0-0 libuuid1 libwrap0 
libx11-6 libx11-data libxapian30 libxau6 libxcb1 libxml2
  libxtables12 linux-image-amd64 locales login logrotate lsb-base 
lsb-release 

Re: firefox palemoon waterfox baselisk problem, not on chromium

[Reco]

Hi.

On Sat, Oct 20, 2018 at 08:20:16AM +0100, mick crane wrote:
> On 2018-10-20 07:22, Reco wrote:
> > Hi.
> > 
> > On Sat, Oct 20, 2018 at 02:16:57AM +0200, arne wrote:
> > > By-passed my proxies, did not help.
> > > 
> > > Those sites all load OK in Chromium, but I do not like this browser.
> > > 
> > > Strange thing, when I retry 2-80 times the pages get loaded.
> > > 
> > > I use Tab Mix Plus Mozilla add-on to reload every 2 seconds until the
> > > pages load.
> > > 
> > > 
> > > In short:
> > > Secure Connection Failed
> > > 
> > > Any ideas what can be the solution?
> > 
> > A better question would be - what's the actual problem.
> > 'Secure Connection Failed' can refer to many things, such as
> > certificate/domain mismatch, certificate expiration, wrong TLS protocol
> > version etc.
> > Any Modern Browser™ hides these details from you, so Firefox (for
> > instance) itself is hardly suited for the troubleshooting.
> > 
> > So I propose this for starters:
> > 
> > openssl s_client -connect www.google.com:443
> > 
> > Reco
> 
> Is this something about google enforcing https everywhere ?

That's a part of the problem, of course. Plain HTTP does not have these
kind of problems (but there are another ones and HTTPS was invented to
solve these).
But I don't have any useful information (yet) to even start
suspecting something.

Reco

Re: firefox palemoon waterfox baselisk problem, not on chromium

[mick crane]

On 2018-10-20 07:22, Reco wrote:

Hi.

On Sat, Oct 20, 2018 at 02:16:57AM +0200, arne wrote:

By-passed my proxies, did not help.

Those sites all load OK in Chromium, but I do not like this browser.

Strange thing, when I retry 2-80 times the pages get loaded.

I use Tab Mix Plus Mozilla add-on to reload every 2 seconds until the
pages load.


In short:
Secure Connection Failed

Any ideas what can be the solution?


A better question would be - what's the actual problem.
'Secure Connection Failed' can refer to many things, such as
certificate/domain mismatch, certificate expiration, wrong TLS protocol
version etc.
Any Modern Browser™ hides these details from you, so Firefox (for
instance) itself is hardly suited for the troubleshooting.

So I propose this for starters:

openssl s_client -connect www.google.com:443

Reco


Is this something about google enforcing https everywhere ?

mick
--
Key ID4BFEBB31