Re: [PLUG] incron issue

2017-11-17 Thread Tom
I am glad you worked it out. Well done.

Darn fast computers!!

-T

On Fri, 2017-11-17 at 18:04 -0800, Denis Heidtmann wrote:
> On the "Create":  this convinces me that I should take up drinking
> coffee,
> so some stronger brain stimulant. Dumb.
> 
> On the multiple entries, I think the issue is that my test script is
> very
> short and fast.  I added a sleep 10 and I get only one entry--the
> first
> one.  Apparently the print driver (or the program calling it) closes
> the
> file multiple times.  I added $% to the incrontab file and %2 to the
> script
> (but w/o the sleep in my script) I got:
> 
> test1 create  test23 IN_CLOSE_WRITE
> test1 create  test23.PLT IN_CLOSE_WRITE
> test1 create  test23.PLT IN_CLOSE_WRITE
> test1 create  test23.PLT IN_CLOSE_WRITE
> 
> This behavior of the driver/application seems not the best, but there
> is
> nothing to be done about it.  I assume that my printing script will
> take
> sufficient time it will not matter.
> 
> I recorded the times associated with the four log entries.  It was
> 347 msec
> overall, with the last step taking most of this time at about 300
> msec.  So
> my anticipation that the multiple writes/closing will not matter
> seems
> reasonable.  Let's hope so.
> 
> Thanks again for the suggestion.
> 
> -Denis
> 
> On Fri, Nov 17, 2017 at 2:02 PM, Tomas Kuchta  il.com>
> wrote:
> 
> > 
> > If I recall incron details correctly, you get multiple entries in
> > your log
> > because you run your script multiple times at different events:
> > IN_CLOSE_WRITE,IN_NO_LOOP
> > 
> > Your other question: You see "create" in your log because that is
> > what your
> > echo command puts there in your script.
> > 
> > -Tomas
> > 
> > On Nov 17, 2017 11:47 AM, "Denis Heidtmann"  > com>
> > wrote:
> > 
> > I have pursued Tomas' advice to use incron to automatically send
> > files
> > written by the win2k print driver to the printer.  I have
> > everything down
> > to one issue.  To test, I have a simple script (intest.sh) that
> > just sends
> > the event responded to to a log file:
> > 
> > #! /bin/bash
> > # test of incron
> > echo "tes1 create " $1 >> /home/denis/incronlog.log
> > 
> > The incron table is:
> > 
> > /home/denis/win2kfiles/Print_files IN_CLOSE_WRITE,IN_NO_LOOP
> > /home/denis/scripts/intest.sh $#
> > 
> > The resulting log is:
> > 
> > tes1 create  test12
> > tes1 create  test12.PLT
> > tes1 create  test12.PLT
> > tes1 create  test12.PLT
> > 
> > It generates multiple entries for one file added (i.e., one print
> > command).  I added  IN_ONESHOT to the incrontab:
> > 
> > /home/denis/win2kfiles/Print_files
> > IN_CLOSE_WRITE,IN_ONESHOT,IN_NO_LOOP
> > /home/denis/scripts/intest.sh $#
> > 
> > I still got multiple entries in the log.
> > 
> > 
> > Questions:
> > Why does the log not say "close" instead of "create"?
> > Why four entries?
> > What might the result be when the script intest.sh is replaced by
> > one that
> > prints and deletes the files?  Will it be called 4 times in rapid
> > succession?
> > 
> > Any suggestions for testing further?
> > 
> > Thanks,
> > -Denis
> > ___
> > PLUG mailing list
> > PLUG@pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> > ___
> > PLUG mailing list
> > PLUG@pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> > 
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] Swapping key functions with .Xmodmap

2017-11-17 Thread Bryan Linton
On 2017-11-16 14:40:50, Rich Shepard  wrote:
> 
>   Since the existing .Xmodmap has the remove commands (which I see in the
> man page) I assume that they're needed for all keys being modified.
> 

I don't think the remove commands are needed for anything except
changing "special" keys, like Caps_Lock, Control, Shift, etc.

The manpage only uses the "add" and "remove" keywords for changing
Caps_Lock and Control, and even then only to add and remove the
"lock" in Caps_Lock and the "control" in control.  The actual
keymappings themselves are changed with the keysym command.

! Swap Caps_Lock and Control_L
!
remove Lock = Caps_Lock
remove Control = Control_L
keysym Control_L = Caps_Lock
keysym Caps_Lock = Control_L
add Lock = Caps_Lock
add Control = Control_L

The other examples given in the manpage don't use "add" or
"remove" and simply remap the keys as-is.

%  xmodmap -e "keysym Multi_key = Multi_key Meta_L"

%  xmodmap -e "keysym Alt_L = Meta_L Alt_L"

%  xmodmap -e "keysym BackSpace = Delete"

! make shift-, be < and shift-. be >
!
keysym comma = comma less
keysym period = period greater

The .xmodmap file I posted previously maps the additional keys on
my keyboard to generate a space when pressed.  I would be surprised
if it didn't work for your keyboard as well, provided the proper
keycodes were exchanged so that they map to the wanted keys on
your own keyboard.

If not, does running "xmodmap -verbose .xmodmap" provide any
additional details?

-- 
Bryan

___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] incron issue

2017-11-17 Thread Denis Heidtmann
On the "Create":  this convinces me that I should take up drinking coffee,
so some stronger brain stimulant. Dumb.

On the multiple entries, I think the issue is that my test script is very
short and fast.  I added a sleep 10 and I get only one entry--the first
one.  Apparently the print driver (or the program calling it) closes the
file multiple times.  I added $% to the incrontab file and %2 to the script
(but w/o the sleep in my script) I got:

test1 create  test23 IN_CLOSE_WRITE
test1 create  test23.PLT IN_CLOSE_WRITE
test1 create  test23.PLT IN_CLOSE_WRITE
test1 create  test23.PLT IN_CLOSE_WRITE

This behavior of the driver/application seems not the best, but there is
nothing to be done about it.  I assume that my printing script will take
sufficient time it will not matter.

I recorded the times associated with the four log entries.  It was 347 msec
overall, with the last step taking most of this time at about 300 msec.  So
my anticipation that the multiple writes/closing will not matter seems
reasonable.  Let's hope so.

Thanks again for the suggestion.

-Denis

On Fri, Nov 17, 2017 at 2:02 PM, Tomas Kuchta 
wrote:

> If I recall incron details correctly, you get multiple entries in your log
> because you run your script multiple times at different events:
> IN_CLOSE_WRITE,IN_NO_LOOP
>
> Your other question: You see "create" in your log because that is what your
> echo command puts there in your script.
>
> -Tomas
>
> On Nov 17, 2017 11:47 AM, "Denis Heidtmann" 
> wrote:
>
> I have pursued Tomas' advice to use incron to automatically send files
> written by the win2k print driver to the printer.  I have everything down
> to one issue.  To test, I have a simple script (intest.sh) that just sends
> the event responded to to a log file:
>
> #! /bin/bash
> # test of incron
> echo "tes1 create " $1 >> /home/denis/incronlog.log
>
> The incron table is:
>
> /home/denis/win2kfiles/Print_files IN_CLOSE_WRITE,IN_NO_LOOP
> /home/denis/scripts/intest.sh $#
>
> The resulting log is:
>
> tes1 create  test12
> tes1 create  test12.PLT
> tes1 create  test12.PLT
> tes1 create  test12.PLT
>
> It generates multiple entries for one file added (i.e., one print
> command).  I added  IN_ONESHOT to the incrontab:
>
> /home/denis/win2kfiles/Print_files IN_CLOSE_WRITE,IN_ONESHOT,IN_NO_LOOP
> /home/denis/scripts/intest.sh $#
>
> I still got multiple entries in the log.
>
>
> Questions:
> Why does the log not say "close" instead of "create"?
> Why four entries?
> What might the result be when the script intest.sh is replaced by one that
> prints and deletes the files?  Will it be called 4 times in rapid
> succession?
>
> Any suggestions for testing further?
>
> Thanks,
> -Denis
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
> ___
> PLUG mailing list
> PLUG@pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] DKIM authentication with alpine

2017-11-17 Thread Rich Shepard

On Fri, 17 Nov 2017, Paul Heinlein wrote:


I think we're talking passed one another.


  D'accord.


DKIM "authentication" won't involve alpine in any way. Mail might be
rejected at the SMTP level by a DKIM-aware milter, e.g.,


  Now that I've done more reading I understand that the MUA doesn't matter.
OpenDKIM needs careful and thoughtful setup, then postfix's main.cf needs to
be modified to use it.


Similarly, filtering software like SpamAssassin has network checks for
performing DKIM verification. You then tell SpamAssassin (or its ilk) how
badly to score messages that don't pass verification.


  I'll learn about this after I get OpenDKIM running correctly and add the
SPF records to my DNS server.

Thanks again,

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] incron issue

2017-11-17 Thread Tomas Kuchta
If I recall incron details correctly, you get multiple entries in your log
because you run your script multiple times at different events:
IN_CLOSE_WRITE,IN_NO_LOOP

Your other question: You see "create" in your log because that is what your
echo command puts there in your script.

-Tomas

On Nov 17, 2017 11:47 AM, "Denis Heidtmann" 
wrote:

I have pursued Tomas' advice to use incron to automatically send files
written by the win2k print driver to the printer.  I have everything down
to one issue.  To test, I have a simple script (intest.sh) that just sends
the event responded to to a log file:

#! /bin/bash
# test of incron
echo "tes1 create " $1 >> /home/denis/incronlog.log

The incron table is:

/home/denis/win2kfiles/Print_files IN_CLOSE_WRITE,IN_NO_LOOP
/home/denis/scripts/intest.sh $#

The resulting log is:

tes1 create  test12
tes1 create  test12.PLT
tes1 create  test12.PLT
tes1 create  test12.PLT

It generates multiple entries for one file added (i.e., one print
command).  I added  IN_ONESHOT to the incrontab:

/home/denis/win2kfiles/Print_files IN_CLOSE_WRITE,IN_ONESHOT,IN_NO_LOOP
/home/denis/scripts/intest.sh $#

I still got multiple entries in the log.


Questions:
Why does the log not say "close" instead of "create"?
Why four entries?
What might the result be when the script intest.sh is replaced by one that
prints and deletes the files?  Will it be called 4 times in rapid
succession?

Any suggestions for testing further?

Thanks,
-Denis
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] DKIM authentication with alpine

2017-11-17 Thread Paul Heinlein

On Fri, 17 Nov 2017, Rich Shepard wrote:


On Fri, 17 Nov 2017, Paul Heinlein wrote:


 By "set alpine to use authentication," do you mean "have alpine send mail
 via an authenticated connection rather than just dumping to sendmail"?


Paul,

 Yep. That's what I mean. I'm still learning the language and the tools.
All this to avoid being greylisted when I send mail to domains that check
for authentication.


 If so, then something like this works:
 smtp-server=mail.appl-ecosys.com:587/user=rshepard/tls


 Where does this go? I'm not forwarding mail through another mail server so
the port should be 25 ... I think. I believe that I need to also set a TXT
record on my DNS server for SPF and, perhaps, one for DMARC. Much to learn
and looking for resources.


 The hostname, port, and security protocols may need adjusting, depending
 on your setup. (If your mail server isn't listening on port 587, you may
 want to look it up.) If you're using straight SSL, that directive might
 look like this:
 smtp-server=mail.appl-ecosys.com:465/user=rshepard/ssl


 I don't know what postfix is using here. I have the router set to forward
incoming mail through port 25; outgoing mail uses teh same port. I've not
explicitly set SSL or TSL for alpine/postfix.


 This all assumes, of course, that your mail server has already been
 configured to handle user authentication...


 I've installed opendkim but have not yet started it.


I think we're talking passed one another.

DKIM "authentication" won't involve alpine in any way. Mail might be 
rejected at the SMTP level by a DKIM-aware milter, e.g.,


https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-dkim-with-postfix-on-debian-wheezy

Similarly, filtering software like SpamAssassin has network checks for 
performing DKIM verification. You then tell SpamAssassin (or its ilk) 
how badly to score messages that don't pass verification.


All Alpine does is read the mail delivered to you. It doesn't make any 
assessments about the worthiness of those messages.


--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


[PLUG] Clinic on Sunday

2017-11-17 Thread wes
Looks like I forgot to send this out on Wednesday. Sorry for the late
notice.

The Linux Clinic is this Sunday, 1-5pm. Bring your ailing systems or
questions and we will try to help, or at least get you pointed in a useful
direction.

Free Geek
1731 SE 10th Ave
Portland, OR 97214

-wes
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


[PLUG] incron issue

2017-11-17 Thread Denis Heidtmann
I have pursued Tomas' advice to use incron to automatically send files
written by the win2k print driver to the printer.  I have everything down
to one issue.  To test, I have a simple script (intest.sh) that just sends
the event responded to to a log file:

#! /bin/bash
# test of incron
echo "tes1 create " $1 >> /home/denis/incronlog.log

The incron table is:

/home/denis/win2kfiles/Print_files IN_CLOSE_WRITE,IN_NO_LOOP
/home/denis/scripts/intest.sh $#

The resulting log is:

tes1 create  test12
tes1 create  test12.PLT
tes1 create  test12.PLT
tes1 create  test12.PLT

It generates multiple entries for one file added (i.e., one print
command).  I added  IN_ONESHOT to the incrontab:

/home/denis/win2kfiles/Print_files IN_CLOSE_WRITE,IN_ONESHOT,IN_NO_LOOP
/home/denis/scripts/intest.sh $#

I still got multiple entries in the log.


Questions:
Why does the log not say "close" instead of "create"?
Why four entries?
What might the result be when the script intest.sh is replaced by one that
prints and deletes the files?  Will it be called 4 times in rapid
succession?

Any suggestions for testing further?

Thanks,
-Denis
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] DKIM authentication with alpine

2017-11-17 Thread Rich Shepard

On Fri, 17 Nov 2017, Paul Heinlein wrote:


By "set alpine to use authentication," do you mean "have alpine send mail
via an authenticated connection rather than just dumping to sendmail"?


Paul,

  Yep. That's what I mean. I'm still learning the language and the tools.
All this to avoid being greylisted when I send mail to domains that check
for authentication.


If so, then something like this works:
smtp-server=mail.appl-ecosys.com:587/user=rshepard/tls


  Where does this go? I'm not forwarding mail through another mail server so
the port should be 25 ... I think. I believe that I need to also set a TXT
record on my DNS server for SPF and, perhaps, one for DMARC. Much to learn
and looking for resources.


The hostname, port, and security protocols may need adjusting, depending
on your setup. (If your mail server isn't listening on port 587, you may
want to look it up.) If you're using straight SSL, that directive might
look like this:
smtp-server=mail.appl-ecosys.com:465/user=rshepard/ssl


  I don't know what postfix is using here. I have the router set to forward
incoming mail through port 25; outgoing mail uses teh same port. I've not
explicitly set SSL or TSL for alpine/postfix.

This all assumes, of course, that your mail server has already been 
configured to handle user authentication...


  I've installed opendkim but have not yet started it.

Thanks,

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] DKIM authentication with alpine

2017-11-17 Thread Paul Heinlein

On Fri, 17 Nov 2017, Rich Shepard wrote:


 I'm adding DKIM to my postfix installation and have /etc/opendkim.conf
identifying my domain as the sender. My web searches on how to set alpine to
use authentication fails to find anything newer than 2009 (which has a dead
link to the dead UDub alpine mail list). I also see nothing in alpine's
setup about authenticating outbound mail; it may be there and I don't
recognize it for what it is.


By "set alpine to use authentication," do you mean "have alpine send 
mail via an authenticated connection rather than just dumping to 
sendmail"?


If so, then something like this works:

smtp-server=mail.appl-ecosys.com:587/user=rshepard/tls

The hostname, port, and security protocols may need adjusting, 
depending on your setup. (If your mail server isn't listening on port 
587, you may want to look it up.) If you're using straight SSL, that 
directive might look like this:


smtp-server=mail.appl-ecosys.com:465/user=rshepard/ssl

This all assumes, of course, that your mail server has already been 
configured to handle user authentication...


--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


[PLUG] DKIM authentication with alpine

2017-11-17 Thread Rich Shepard

  I'm adding DKIM to my postfix installation and have /etc/opendkim.conf
identifying my domain as the sender. My web searches on how to set alpine to
use authentication fails to find anything newer than 2009 (which has a dead
link to the dead UDub alpine mail list). I also see nothing in alpine's
setup about authenticating outbound mail; it may be there and I don't
recognize it for what it is.

  Pointers and suggestions are solicited.

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug


Re: [PLUG] Firefox crash when visiting aliexpress

2017-11-17 Thread Rich Shepard

On Thu, 16 Nov 2017, Rich Shepard wrote:


 The 32-bit version of the same release (on Slackware-14.2) does not
crash.


Galen,

  Slackware released firefox-54.5 last night; perhaps an upgrade is
available for CentOS and has fixed the 54.4's dislike of aliexpress.

Rich
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug