Re: Debian home security programs?

[der.hans]

Am 04. May, 2018 schwätzte Karen Lewellen so:

moin moin Karen,

it's certainly possible. A decade ago a friend of mine used debian and
asterisk to setup a bell and intercom system for a school using voip
phones.

Also, I talked to NextClouders at SCaLE and they were talking about
web-statndards based video chat using NextCloud on debian. There's
probably an option for voice only, but it might be easier to do video.

Hmm, I should do something like this too :).

A search for 'raspberry pi sip intercom' turned up several projects.

ciao,

der.hans


Hi everyone,
I am wondering, given how flexible Debian can be, if this idea is possible? 
If it does not already exist?
I now live  in an apartment  above a business that closes very early.  One 
thing I miss from my old dwelling
is a sort of intercom where  people would buzz my code  which dialed my land 
line   phone allowing me to communicate with them before, at that time, 
letting them in the building.
So, I am wondering if I could combine a Linux home security program with a 
wireless intercom,  or doorbell / intercom combination that might  create the 
same effect?
I am not interested in video, just a way to  connect  with a person at my 
door if that makes sense.

thoughts?
Karen



--
#  https://www.LuftHans.com   https://www.PhxLinux.org
#  "If you want to build a ship, don’t drum up people to collect wood, and
#  don’t assign them tasks and work, but rather teach them to long for the
#  endless immensity of the sea." - Antoine de Saint-Exupéry

Debian home security programs?

[Karen Lewellen]

Hi everyone,
I am wondering, given how flexible Debian can be, if this idea is possible? 
If it does not already exist?
I now live  in an apartment  above a business that closes very early.  One 
thing I miss from my old dwelling
 is a sort of intercom where  people would buzz my code  which dialed my 
land line   phone allowing me to communicate with them before, at that 
time, letting them in the building.
So, I am wondering if I could combine a Linux home security program with a 
wireless intercom,  or doorbell / intercom combination that might  create 
the same effect?
I am not interested in video, just a way to  connect  with a person at my 
door if that makes sense.

thoughts?
Karen

[SECURITY] [DSA 2038-1] New pidgin packages fix denial of service

[Thijs Kinkhorst]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- 
Debian Security Advisory DSA-2038-1  secur...@debian.org
http://www.debian.org/security/  Thijs Kinkhorst
April 18, 2010http://www.debian.org/security/faq
- 

Package: pidgin
Vulnerability  : several
Problem type   : remote
Debian-specific: no
CVE Id(s)  : CVE-2010-0420 CVE-2010-0423
Debian Bug : 566775

Several remote vulnerabilities have been discovered in Pidgin, a multi
protocol instant messaging client. The Common Vulnerabilities and
Exposures project identifies the following problems:

CVE-2010-0420

Crafted nicknames in the XMPP protocol can crash Pidgin remotely.

CVE-2010-0423

Remote contacts may send too many custom smilies, crashing Pidgin.

Since a few months, Microsoft's servers for MSN have changed the protocol,
making Pidgin non-functional for use with MSN. It is not feasible to port
these changes to the version of Pidgin in Debian Lenny. This update
formalises that situation by disabling the protocol in the client. Users
of the MSN protocol are advised to use the version of Pidgin in the
repositories of www.backports.org.

For the stable distribution (lenny), these problems have been fixed in
version 2.4.3-4lenny6.

For the unstable distribution (sid), these problems have been fixed in
version 2.6.6-1.

We recommend that you upgrade your pidgin package.

Upgrade instructions
- 

wget url
will fetch the file for you
dpkg -i file.deb
will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given below:

apt-get update
will update the internal database
apt-get upgrade
will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 5.0 alias lenny
- 

Source archives:

  http://security.debian.org/pool/updates/main/p/pidgin/pidgin_2.4.3.orig.tar.gz
Size/MD5 checksum: 13123610 d0e0bd218fbc67df8b2eca2f21fcd427
  http://security.debian.org/pool/updates/main/p/pidgin/pidgin_2.4.3-4lenny6.dsc
Size/MD5 checksum: 1784 f640f8119ef901c7be009232c6dfee05
  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin_2.4.3-4lenny6.diff.gz
Size/MD5 checksum:72144 85217de41bcd069748eb441886cdfab9

Architecture independent packages:

  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin-data_2.4.3-4lenny6_all.deb
Size/MD5 checksum:  7019074 1c79c0da4c115e2699d577b957c4e541
  
http://security.debian.org/pool/updates/main/p/pidgin/finch-dev_2.4.3-4lenny6_all.deb
Size/MD5 checksum:   159726 c657bace836fb1d4f3c04c57bdcd7e19
  
http://security.debian.org/pool/updates/main/p/pidgin/libpurple-bin_2.4.3-4lenny6_all.deb
Size/MD5 checksum:   133894 49e2b54dcad5a2b40705478118da2d72
  
http://security.debian.org/pool/updates/main/p/pidgin/libpurple-dev_2.4.3-4lenny6_all.deb
Size/MD5 checksum:   277220 9517eadf780382575efcd57ba9dc308b
  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin-dev_2.4.3-4lenny6_all.deb
Size/MD5 checksum:   193802 b05666d23964d0d28646dc49a85de940

alpha architecture (DEC Alpha)

  
http://security.debian.org/pool/updates/main/p/pidgin/libpurple0_2.4.3-4lenny6_alpha.deb
Size/MD5 checksum:  1477324 c6c9e6753f98159748b9e0116bb40df3
  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin_2.4.3-4lenny6_alpha.deb
Size/MD5 checksum:   776550 1334935aee6756fdc1b6e1702cabe0b3
  
http://security.debian.org/pool/updates/main/p/pidgin/finch_2.4.3-4lenny6_alpha.deb
Size/MD5 checksum:   369734 f54c236b4aa7e94d33da983f042bd82b
  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin-dbg_2.4.3-4lenny6_alpha.deb
Size/MD5 checksum:  4952616 ac34a66c4b19a7dd23b1fa0240c07f97

amd64 architecture (AMD x86_64 (AMD64))

  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin_2.4.3-4lenny6_amd64.deb
Size/MD5 checksum:   727918 e6447c0efc4f5c490bc806f00840b075
  
http://security.debian.org/pool/updates/main/p/pidgin/libpurple0_2.4.3-4lenny6_amd64.deb
Size/MD5 checksum:  1406192 68711767e43c6a0722b8b4d5ed59843a
  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin-dbg_2.4.3-4lenny6_amd64.deb
Size/MD5 checksum:  5067988 c430e8ff4e8b13830c71da4f6948a4f6
  
http://security.debian.org/pool/updates/main/p/pidgin/finch_2.4.3-4lenny6_amd64.deb
Size/MD5 checksum:   348062 042092eae5df409b1b39ae96a6a5b856

arm architecture (ARM)

  
http://security.debian.org/pool/updates/main/p/pidgin/libpurple0_2.4.3-4lenny6_arm.deb
Size/MD5 checksum:  1217972 2b2879660723d31097c9a535e14c177d
  
http://security.debian.org/pool/updates/main/p/pidgin/pidgin_2.4.3-4lenny6_arm.deb
Size/MD5 checksum:   

problem to put the soho plasmoid

[BasaBuru]

helo

I can't put in the desktop the soho and solar system.

See me the initializacion script is fail.

I think i need few packets but i don't now how.

thanks

BasaBuru


-- 
To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100529.06030.basab...@basatu.org

backports on kernel 4.15 and nvidia-driver 390 crashes x

[Boyan Penkov]

Hello,

I have upgraded to the current stretch backports nvidia-driver, and this 
crashes on the current stretch backports kernel.  Have folks seen this 
combination work?

I see the following:

kernel — nvidia — status
4.15 — 390 — fail
4.15 — 370 — untested
4.9 — 390 — fail
4.9 — 375 — success

Anything I can do to help debug? What’s annoying is that the fails on 390 print 
a blank screen with no X cursor and a prompt to log out, so I don’t know where 
to look for logs or traces….

Cheers!
--
Boyan Penkov
www.boyanpenkov.com

Re: Jessie: No logrotate since October 2016?

[Boyan Penkov]

Really late response here, but thanks — some reading of /etc/anacrontab and 
run-parts does make clear that edits of the crontab will then be run by anacron

Thanks kindly!
--
Boyan Penkov
www.boyanpenkov.com

> On Apr 24, 2018, at 14:27, Brad Rogers  wrote:
> 
> On Tue, 24 Apr 2018 14:09:06 -0400
> Boyan Penkov  wrote:
> 
> Hello Boyan,
> 
>> that this is the case, and automatically read the crontab, then write
>> an intelligent anacrontab with sane defaults?
> 
> From the anacron page on packages.debian.org;
> 
> This package is pre-configured to execute the daily jobs of the Debian
> system. You should install this program if your system isn't powered on
> 24 hours a day to make sure the maintenance jobs of other Debian
> packages are executed each day.
> 
> Not a full answer, but gets you part way to where you want to be, I hope.
> 
> -- 
> Regards  _
> / )   "The blindingly obvious is
>/ _)radnever immediately apparent"
> You're only laughing 'cause you haven't heard the news
> Sleeep - Wah!

Re: RETIRAR NOME DA LISTA

[Carlos Donizete Froes]

Ola Wallyson e Marcos, blz!

> Favor o meu também. Grato
> 
> Em 3 de maio de 2018 18:23, Marcos Lima  escreveu:
> > FAVOR RETIRA MEU NOME DA LISTA DE E-MAILS DESTE GRUPO.

Para se retirar da lista. Acesse este link:

https://lists.debian.org/debian-user-portuguese/

Coloque seu email e clique no Unsubscribe.

Espero ter ajudado, ate mais!

-- 
⢀⣴⠾⠻⢶⣦⠀  Carlos Donizete Froes (a.k.a coringao) 
⣾⠁⢠⠒⠀⣿⡁  Fingerprint: 2157 630B D441 A775 BEFF  D35F FA63 ADA6 B638 B780
⢿⡄⠘⠷⠚⠋⠀  Debian Wiki: https://wiki.debian.org/coringao
⠈⠳⣄

signature.asc
Description: This is a digitally signed message part

Re: RETIRAR NOME DA LISTA

[Wallyson Freitas]

Favor o meu também. Grato

Em 3 de maio de 2018 18:23, Marcos Lima  escreveu:

> FAVOR RETIRA MEU NOME DA LISTA DE E-MAILS DESTE GRUPO.
> --
> *Marcos Lima.*
> *(71)98811-2805*
>



-- 
*Wallyson Freitas*
Gerente Centro de processamento de Dados - CPD
*E-mail*: *c...@armazemcentrooeste.com.br *
*Tel:(*61)3453-9404
*SPE**KY:* wallysonfreitas

RETIRAR NOME DA LISTA

[Marcos Lima]

FAVOR RETIRA MEU NOME DA LISTA DE E-MAILS DESTE GRUPO.
-- 
*Marcos Lima.*
*(71)98811-2805*

Re: gegl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0: undefined symbol: babl_process_rows

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, May 03, 2018 at 09:13:28PM +0200, Johann Spies wrote:
> Thanks Sven and Tomas.  You have helped me to identify the problem:
> indeed a version of libbabl in /usr/local!
> 
> I must have asked earlier then I would not have spent hours on this problem! 
> :)

Glad it helped :-)

- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrrYScACgkQBcgs9XrR2kYkYgCcD9IWA4we6pBB/MuWf3W3+vnw
434An0rVdwTrMEa7dtCwH/A7AZzZPcHG
=mpVK
-END PGP SIGNATURE-

Re: gegl: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0: undefined symbol: babl_process_rows

[Johann Spies]

Thanks Sven and Tomas.  You have helped me to identify the problem:
indeed a version of libbabl in /usr/local!

I must have asked earlier then I would not have spent hours on this problem! :)

Regards
Johann

Re: Debian mirror problem? was [Re: Debian glossary?]

[Richard Owlett]

On 05/03/2018 12:28 PM, Brian wrote:

On Thu 03 May 2018 at 09:27:52 -0500, Richard Owlett wrote:
[snip]


My interpretation is that on my original visit I saw a defective mirror.

If a similar symptom appears in the future, is there any way to determine
which mirror I'm seeing?


I use Firefox. Prior to activating a link I would do

  netstat -tulpan | grep ESTABLISHED.*firefox

Immediately after activation, the command would be repeated. 'whois'
would then dtermine what has been connected to.



David has likely spotted my problem.
Getting to get familiar with netstat will be valuable.
Thank you.

Re: Debian mirror problem? was [Re: Debian glossary?]

[Richard Owlett]

On 05/03/2018 01:17 PM, David Wright wrote:

On Thu 03 May 2018 at 09:27:52 (-0500), Richard Owlett wrote:

On 04/30/2018 07:28 PM, David Wright wrote:

[*SNIP*]
I only saw a misunderstanding of how man pages impart information.
[*SNIP*]


On 04/30/2018 09:27 AM, Richard Owlett wrote:

The relevant line of the HTML of 
https://manpages.debian.org/stretch/coreutils/ls.1.en.html is


GNU coreutils online help: http://www.gnu.org/software/coreutils/;>http://www.gnu.org/software/coreutils/

and www.gnu.org/software/coreutils/ gives no navigational guidance.


Today {AND every time I've gone the there after my post} the
relevant line of
   https://manpages.debian.org/stretch/coreutils/ls.1.en.html
reads:


Full documentation at: http://www.gnu.org/software/coreutils/ls;>http://www.gnu.org/software/coreutils/ls



My interpretation is that on my original visit I saw a defective mirror.


Revisiting your two posts, you are commenting on two different places
on the web page.

First post Date: Mon, 30 Apr 2018 15:15:41 -0500:

REPORTING BUGS
GNU coreutils online help: 

Second post Date: Thu, 3 May 2018 09:27:52 -0500:

SEE ALSO
Full documentation at: 

Perhaps the fact that "coreutils" happens to end with "ls" confuses
the eye.


Possibly. But my memory had me convinced that I had searched for "Full 
documentation at:" each time.

Thank you.





If a similar symptom appears in the future, is there any way to
determine which mirror I'm seeing?


Cheers,
David.

Re: Debian mirror problem? was [Re: Debian glossary?]

[David Wright]

On Thu 03 May 2018 at 09:27:52 (-0500), Richard Owlett wrote:
> On 04/30/2018 07:28 PM, David Wright wrote:
> >[*SNIP*]
> >I only saw a misunderstanding of how man pages impart information.
> >[*SNIP*]
> 
> On 04/30/2018 09:27 AM, Richard Owlett wrote:
> >The relevant line of the HTML of 
> >https://manpages.debian.org/stretch/coreutils/ls.1.en.html is
> >
> >
> >GNU coreutils online help:  >href="http://www.gnu.org/software/coreutils/;>http://www.gnu.org/software/coreutils/
> >
> >and www.gnu.org/software/coreutils/ gives no navigational guidance.
> 
> Today {AND every time I've gone the there after my post} the
> relevant line of
>   https://manpages.debian.org/stretch/coreutils/ls.1.en.html
> reads:
> >
> >Full documentation at:  >href="http://www.gnu.org/software/coreutils/ls;>http://www.gnu.org/software/coreutils/ls
> 
> 
> My interpretation is that on my original visit I saw a defective mirror.

Revisiting your two posts, you are commenting on two different places
on the web page.

First post Date: Mon, 30 Apr 2018 15:15:41 -0500:

REPORTING BUGS
GNU coreutils online help: 

Second post Date: Thu, 3 May 2018 09:27:52 -0500:

SEE ALSO
Full documentation at:  

Perhaps the fact that "coreutils" happens to end with "ls" confuses
the eye.

> If a similar symptom appears in the future, is there any way to
> determine which mirror I'm seeing?

Cheers,
David.

Re: Debian mirror problem? was [Re: Debian glossary?]

[Brian]

On Thu 03 May 2018 at 09:27:52 -0500, Richard Owlett wrote:

> On 04/30/2018 07:28 PM, David Wright wrote:
> > [*SNIP*]
> > I only saw a misunderstanding of how man pages impart information.
> > [*SNIP*]
> 
> On 04/30/2018 09:27 AM, Richard Owlett wrote:
> > The relevant line of the HTML of 
> > https://manpages.debian.org/stretch/coreutils/ls.1.en.html is
> > 
> > 
> > GNU coreutils online help:  > href="http://www.gnu.org/software/coreutils/;>http://www.gnu.org/software/coreutils/
> > 
> > and www.gnu.org/software/coreutils/ gives no navigational guidance.
> 
> Today {AND every time I've gone the there after my post} the relevant line
> of
>   https://manpages.debian.org/stretch/coreutils/ls.1.en.html
> reads:
> > 
> > Full documentation at:  > href="http://www.gnu.org/software/coreutils/ls;>http://www.gnu.org/software/coreutils/ls
> 
> 
> My interpretation is that on my original visit I saw a defective mirror.
> 
> If a similar symptom appears in the future, is there any way to determine
> which mirror I'm seeing?

I use Firefox. Prior to activating a link I would do

 netstat -tulpan | grep ESTABLISHED.*firefox

Immediately after activation, the command would be repeated. 'whois'
would then dtermine what has been connected to.

-- 
Brian.

Re: Debian glossary?

[Richard Owlett]

On 04/30/2018 10:02 AM, David Wright wrote:

On Mon 30 Apr 2018 at 06:46:01 (-0500), Richard Owlett wrote:

[snip]

Comments?


Sure. You turn to page 108 of Running Linux 5th ed and read it there.

Don't have it? Download it. Type running-linux-5th-2006.pdf into
google and it's the first hit. Then type

$ wget 
https://the-eye.eu/public/Books/IT%20Various/running_linux_5th_edition.pdf

and read it.


I've downloaded it and bookmarked https://the-eye.eu/public/ for future 
reference. As I've written I have discovered ~1500 pages of "dead 
trees". That includes a 2002 copy of _A Practical Guide to Red Hat 
Linux_ by Sobell [no idea when acquired]. I'll start on both - the dead 
tree version can be more Vietcong to read.





Why "running-linux-5th-2006.pdf"? Because that's the name it has in my
filesystem. (I gave away my July 1995 paper copy to an enthusiastic
teenager who now works in IT.) Now get stuck into Unix Power Tools
3rd edition (replaces my October 1995 edition), Linux in a Nutshell
(ditto April 1997), and several others out there, all downloadable,
usually in slightly dated editions.

I thought you had a voracious appetite for reading in your retirement.



I have a tendency to read for the "question-du-jour", missing other 
information.

The result is spotty background.


I just don't understand how you can hang out hereabouts for over six
years and not know that d stands for directory, or claim to be
"uninitiated".

Cheers,
David.

eCryptfs para cifrar el home

[Angel Vicente]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hola a todos.

¿Ha usado alguien eCryptFs para cifrar el directorio de usuario
en /home?

He visto que se puede usar en Ubuntu pero que no desmonta al cerrar la
sesión de cada usuario, como parece que tiene algo que ver con systemd,
supongo que en Debian pasará algo similar.

Saludos y gracias de antemano

- -- 
Key fingerprint 01DC 0386 2B28 0A02 A270 E243 008B AABF 1822 9851
-BEGIN PGP SIGNATURE-

iHUEAREIAB0WIQQB3AOGKygKAqJw4kMAi6q/GCKYUQUCWusZagAKCRAAi6q/GCKY
UUcQAP4syetCuayz3ZSlZmPBKr3h0t05torPHwbtufwrnQiGaQD5ATXDWYcblSLT
eWTMTwk5oo93BoXxgKm1raovL/KlCk8=
=tLXw
-END PGP SIGNATURE-

Debian mirror problem? was [Re: Debian glossary?]

[Richard Owlett]

On 04/30/2018 07:28 PM, David Wright wrote:

[*SNIP*]
I only saw a misunderstanding of how man pages impart information.
[*SNIP*]


On 04/30/2018 09:27 AM, Richard Owlett wrote:

The relevant line of the HTML of 
https://manpages.debian.org/stretch/coreutils/ls.1.en.html is


GNU coreutils online help: http://www.gnu.org/software/coreutils/;>http://www.gnu.org/software/coreutils/

and www.gnu.org/software/coreutils/ gives no navigational guidance.


Today {AND every time I've gone the there after my post} the relevant 
line of

  https://manpages.debian.org/stretch/coreutils/ls.1.en.html
reads:


Full documentation at: http://www.gnu.org/software/coreutils/ls;>http://www.gnu.org/software/coreutils/ls



My interpretation is that on my original visit I saw a defective mirror.

If a similar symptom appears in the future, is there any way to 
determine which mirror I'm seeing?


TIA

Re: Connexion automatique à une cible iSCSI

[BERTRAND Joël]

Felix Defrance a écrit :
> Salut,
> 
> Que dit un "systemctl is-enabled open-iscsi.service" ?

enabled.

Mais le problème n'est pas là, pour l'instant, je lance iscsid à la main
(iscsid -f -d3).

Merci tout de même ;-)

Bien cordialement,

JKB

Re: Connexion automatique à une cible iSCSI

[Felix Defrance]

Salut,

Que dit un "systemctl is-enabled open-iscsi.service" ?


Le 03/05/2018 à 11:54, BERTRAND Joël a écrit :
>   Bonjour à tous.
>
>   Je suis en train de monter un système de sauvegarde avec un NAS QNAP et
> Bacula pour remplacer un antique système de sauvegarde tournant déjà
> avec Bacula, mais adossé à une baie de vingt disques U320...
>
>   J'avoue avoir été bluffé par ces petits NAS. J'ai désactivé sur le NAS
> tous les protocoles sauf iSCSI. Je l'ai configuré et j'ai configuré côté
> Linux l'initiateur.
>
>   J'arrive à me connecter et à utiliser LUN sur le NAS. Cependant,
> j'aimerais automatiser le montage du NAS au boot du système et je n'y
> arrive pas. Pourtant, j'utilisais le montage automatique par le passé
> sans problème. Ne faisant pas cela tous les jours, je suppose que j'ai
> raté quelque chose, mais je n'ai pas trouvé de solution efficace.
>
>   Mon fichier de configuration :
>
> iscsid.startup = /sbin/iscsid
> iscsid.safe_logout = Yes
> node.startup = automatic
> node.leading_login = No
> node.session.auth.authmethod = None
> discovery.sendtargets.auth.authmethod = None
> node.session.timeo.replacement_timeout = 120
> node.conn[0].timeo.login_timeout = 15
> node.conn[0].timeo.logout_timeout = 15
> node.conn[0].timeo.noop_out_interval = 5
> node.conn[0].timeo.noop_out_timeout = 5
> node.session.err_timeo.abort_timeout = 15
> node.session.err_timeo.lu_reset_timeout = 30
> node.session.err_timeo.tgt_reset_timeout = 30
> node.session.initial_login_retry_max = 8
> node.session.cmds_max = 128
> node.session.queue_depth = 32
> node.session.xmit_thread_priority = -20
> node.session.iscsi.InitialR2T = No
> node.session.iscsi.ImmediateData = Yes
> node.session.iscsi.FirstBurstLength = 262144
> node.session.iscsi.MaxBurstLength = 16776192
> node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144
> node.conn[0].iscsi.MaxXmitDataSegmentLength = 0
> discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
> node.session.nr_sessions = 1
> node.session.iscsi.FastAbort = Yes
>
>   Naturellement, j'ai bien effectué l'opération de découverte des LUN et
> relancé iscsid. Rien n'y fait.
>
>   Une idée ?
>
>   JKB
>

-- 
Félix Defrance
PGP: 0x0F04DC57

Re: Packagekit spamming syslog

[Tony van der Hoff]

On 02/05/18 17:52, Kenneth Parker wrote:
> You might want to bring this up, on the Packagekit email list:
>
> http://lists.freedesktop.org/mailman/listinfo/packagekit
>
> (Note:  I am not a Packagekit expert.  I got this from the Debian Wiki
> Page on Packagekit).
>
> Kenneth Parker 
>
> On Wed, May 2, 2018, 11:30 AM Tony van der Hoff  > wrote:
>
> Running fully up to date stretch, I'm seeing the following in my
> syslog
> every 5 minutes:
>
> May  2 15:55:25 tony-lx PackageKit: refresh-cache transaction
> /144833_aadbeecc from uid 1000 finished with success after 2225ms
> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
> /144834_dacaaceb from uid 1000 finished with success after 1502ms
> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
> /144835_cdcacaca from uid 1000 finished with success after 452ms
> May  2 15:55:28 tony-lx PackageKit: get-updates transaction
> /144837_aabccdcd from uid 1000 finished with success after 496ms
> May  2 15:55:29 tony-lx PackageKit: get-updates transaction
> /144838_bddedcad from uid 1000 finished with success after 451ms
>
> Can someone please explain why PackageKit needs to update so
> often, and
> maybe how to tame it.
>
> Thanks,
> Tony
>
> -- 
> Tony van der Hoff    | mailto:t...@vanderhoff.org
> 
> Buckinghamshire, England |
>
Thanks for replying, Kenneth. Whilst not solved, I think I'm out of the
woods. See my reply to Curt for the details.

-- 
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |

Re: Packagekit spamming syslog

[Tony van der Hoff]

On 02/05/18 17:19, Curt wrote:
> On 2018-05-02, Tony van der Hoff  wrote:
>> Running fully up to date stretch, I'm seeing the following in my syslog
>> every 5 minutes:
>>
>> May  2 15:55:25 tony-lx PackageKit: refresh-cache transaction
>> /144833_aadbeecc from uid 1000 finished with success after 2225ms
>> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
>> /144834_dacaaceb from uid 1000 finished with success after 1502ms
>> May  2 15:55:27 tony-lx PackageKit: get-updates transaction
>> /144835_cdcacaca from uid 1000 finished with success after 452ms
>> May  2 15:55:28 tony-lx PackageKit: get-updates transaction
>> /144837_aabccdcd from uid 1000 finished with success after 496ms
>> May  2 15:55:29 tony-lx PackageKit: get-updates transaction
>> /144838_bddedcad from uid 1000 finished with success after 451ms
>>
>> Can someone please explain why PackageKit needs to update so often, and
>> maybe how to tame it.
> There's a bug report looks relevant:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881787
>
> Jason Rodrigues in that thread suspects the KDE update notifier (he
> removed 'apper', finding no other palliative measure).
>
> Of course if you're not running KDE (or apper) it must be--implacable
> logic--something else.
Thanks for your reply, Curt.I saw that bug report, and uninstalled
Apper, but no difference, so I re-installed it. I am indeed running KDE,
but see no option to control this behaviour.

I have to add that I initially became aware of this because my syslog
had grown to 26GiB, and I unfairly blamed it on these messages. I then
reconfigured logrotate, and the syslog is now kept to a more reasonable
size, so the problem is no longer significant..

Thanks again for your interest.
 Tony

Connexion automatique à une cible iSCSI

[BERTRAND Joël]

Bonjour à tous.

Je suis en train de monter un système de sauvegarde avec un NAS QNAP et
Bacula pour remplacer un antique système de sauvegarde tournant déjà
avec Bacula, mais adossé à une baie de vingt disques U320...

J'avoue avoir été bluffé par ces petits NAS. J'ai désactivé sur le NAS
tous les protocoles sauf iSCSI. Je l'ai configuré et j'ai configuré côté
Linux l'initiateur.

J'arrive à me connecter et à utiliser LUN sur le NAS. Cependant,
j'aimerais automatiser le montage du NAS au boot du système et je n'y
arrive pas. Pourtant, j'utilisais le montage automatique par le passé
sans problème. Ne faisant pas cela tous les jours, je suppose que j'ai
raté quelque chose, mais je n'ai pas trouvé de solution efficace.

Mon fichier de configuration :

iscsid.startup = /sbin/iscsid
iscsid.safe_logout = Yes
node.startup = automatic
node.leading_login = No
node.session.auth.authmethod = None
discovery.sendtargets.auth.authmethod = None
node.session.timeo.replacement_timeout = 120
node.conn[0].timeo.login_timeout = 15
node.conn[0].timeo.logout_timeout = 15
node.conn[0].timeo.noop_out_interval = 5
node.conn[0].timeo.noop_out_timeout = 5
node.session.err_timeo.abort_timeout = 15
node.session.err_timeo.lu_reset_timeout = 30
node.session.err_timeo.tgt_reset_timeout = 30
node.session.initial_login_retry_max = 8
node.session.cmds_max = 128
node.session.queue_depth = 32
node.session.xmit_thread_priority = -20
node.session.iscsi.InitialR2T = No
node.session.iscsi.ImmediateData = Yes
node.session.iscsi.FirstBurstLength = 262144
node.session.iscsi.MaxBurstLength = 16776192
node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144
node.conn[0].iscsi.MaxXmitDataSegmentLength = 0
discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
node.session.nr_sessions = 1
node.session.iscsi.FastAbort = Yes

Naturellement, j'ai bien effectué l'opération de découverte des LUN et
relancé iscsid. Rien n'y fait.

Une idée ?

JKB