Re: A full /var partition destroyed 3 hours of my life!

2016-11-14 Thread Peter Ludikovsky
Am 15.11.2016 um 06:00 schrieb Borden Rhodes:
> I start blindly casting whatever btrfs spells I can find on the
> Internet to fix 'no space left on device' errors. One of them
> eventually works and df -h correctly reports the free space in my /var
> partition and Debian boots normally again.
> 
> My question, therefore, is whether this is a btrfs bug that got
> triggered by the full /var partition or whether Debian is designed to
> break irrecoverably when /var fills up. Any ideas of what happened?
> 

Does anything on the Debian Wiki on Btrfs [1] seem familiar? Other than
that I can only guess, but maybe check the SMART information of your
disk(s) for excessive errors, as it _could_ be that defective sectors
prevent Btrfs from doing it's COW magic.


[1] https://wiki.debian.org/Btrfs#WARNINGS



signature.asc
Description: OpenPGP digital signature


Re: A full /var partition destroyed 3 hours of my life!

2016-11-14 Thread Michael Biebl
[rsyslog maintainer speaking here]

Am 15.11.2016 um 06:00 schrieb Borden Rhodes:
> One of the culprits in my full /var partition was a 3 gig syslog file
> which has only been getting bigger since January despite running
> logrotate -f. I try to run it this time but I'm told that it can't

I'd be interested to find out, why logrotation was not done
automatically. Do you have cron installed and running?
Do you have  /etc/cron.daily/logrotate which works when executed and a
corresponding /etc/logrotate.d/rsyslog?

Any idea why logrotate was not run or failed to do its job?

> My question, therefore, is whether this is a btrfs bug that got
> triggered by the full /var partition or whether Debian is designed to
> break irrecoverably when /var fills up. Any ideas of what happened?
> 

That sounds like a btrfs issue. Which kernel is that?
I do remember btrfs having problems when the disk runs full.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


A full /var partition destroyed 3 hours of my life!

2016-11-14 Thread Borden Rhodes
I tried booting up into Debian and got all sorts of systemd breakages
apparently because my /var partition was full. That's fair, but the
pain started when Debian frustrated any attempt to free up space. I'm
wondering if this is a 'feature' that needs removing or if there might
be a bug in the underlying filesystem. I really don't want anymore
finite hours of my life (or anyone else's) lost in this problem if I
can find the cause.

One of the culprits in my full /var partition was a 3 gig syslog file
which has only been getting bigger since January despite running
logrotate -f. I try to run it this time but I'm told that it can't
rotate anything because there's no space left of the device. OK, Plan
B. Another thing that the interwebs say is to run apt-get clean to
sweep out downloaded packages, of which I collected hundreds of
megabytes. Again, this command failed because there was no space left
on the device.

Since there's almost no documentation as to what can be safely rm'd in
/var without breaking your system, I decide the least risky choice is
to sudo rm -rf the offending 3-gig syslog file from single-user mode
and the systemd debug shell. But *THIS* command failed because there
was 'no space left on the device'. Is this right? Does rm need space
on a drive to free other space? If so, how on earth can you fix a full
partition if you can't remove anything from it?!

Since Debian can't delete files from its own partitions, I have to
boot from a Ubuntu DVD. I'm able to rm -rf the syslog file from that,
but when I reboot into Debian, I get the same 'no space left on
device' errors. That's weird, so I df -h to figure out what's going on
and df correctly reports a 5G var partition, of which under 3G are now
used and avail space is 0G. Whoa, wait, what?!?! How can 5G - 3G =
0G?!

I start blindly casting whatever btrfs spells I can find on the
Internet to fix 'no space left on device' errors. One of them
eventually works and df -h correctly reports the free space in my /var
partition and Debian boots normally again.

My question, therefore, is whether this is a btrfs bug that got
triggered by the full /var partition or whether Debian is designed to
break irrecoverably when /var fills up. Any ideas of what happened?



Re: Movie problem

2016-11-14 Thread Jimmy Johnson

On 11/14/2016 05:54 PM, Gene Heskett wrote:

Hi all;

Background;
Need to submit to the alibaba site, a movie demonstration the broken
video coming out of an Orange-pi-plus-2e.

Camera is a Sony Digital Hi-8 Handycam, firewire interface.
Raw video is bulky as its a digital format, full resolution of 720x480.
so its close to 6 gigabytes a running minute when captured over the
firewire port.

The only movie editor we have, that can also control this camera for
start/stop/capture etc, is kino. No other movie prosessing utility we
have has ever been in the same county as a firewire port

Web submission site at aliexpress.com has no clue what to do with a a
raw-dv file and refuses to take it as an evidence submission.

Kino, as in running on a fully uptodate wheezy, apparently can't find
ffmpeg to make the conversion when I attempt to export this 1 minutes
worth of raw-dv format video.  ffmpeg and all its friends are installed.
But in kino, the whole page of mpeg4 options is ghosted out.

Does anybody have a clue what I should sniff about for next?

Thanks & Cheers, Gene Heskett


Gene you'll probable find what you need here,
"deb http://www.deb-multimedia.org/ wheezy main non-free"

regards,
--
Jimmy Johnson

Debian - Wheezy - KDE 4.8.4 - AMD64 - EXT4 at sda1
Registered Linux User #380263



Re: Movie problem

2016-11-14 Thread David Christensen
On 11/14/2016 05:54 PM, Gene Heskett wrote:
> Need to submit to the alibaba site, a movie demonstration the broken 
> video coming out of an Orange-pi-plus-2e.
> 
> Camera is a Sony Digital Hi-8 Handycam, firewire interface.

One of the reasons I keep a working Windows XP system drive is for
Windows Movie Maker.  I used it to capture video from a Canon 720x480 DV
camcorder with Firewire output.  I could then edit as desired and output
video in various formats and resolutions.


David



Re: SUCESS!!! - was [Re: Progress report Re: Invoking ddrescue]

2016-11-14 Thread Richard Owlett

On 11/14/2016 5:20 PM, Brian wrote:

On Mon 14 Nov 2016 at 16:29:52 -0600, Richard Owlett wrote:


ddrescue has run to completion without _reported_ errors for all partitions
of the drive. I understand that does *NOT* guarantee that the files are not
corrupt.

I've read the man page of su with recent experiences in mind.
I agree with tomas that some of my recent problems relate to the differences
between "su" and "su --login".


tomas did not say he agreed that any of your recent problems relate
to the differences between "su" and "su --login". He explained the
difference between "su" and "su -", a factual matter.

Speaking of facts: we've had the appearance of subtle differences and
matching observed symptoms. Fuzzy. Nothing concrete and nothing that
doesn't involve speculation or possibly misobservation. As far as I am
concerned, all the commands used to carry out your task can be issued
successfully as root or after a su to root.



gee whiz what insight
writen by some one who actually read my reply to 
tomas?






Movie problem

2016-11-14 Thread Gene Heskett
Hi all;

Background;
Need to submit to the alibaba site, a movie demonstration the broken 
video coming out of an Orange-pi-plus-2e.

Camera is a Sony Digital Hi-8 Handycam, firewire interface.
Raw video is bulky as its a digital format, full resolution of 720x480. 
so its close to 6 gigabytes a running minute when captured over the 
firewire port.

The only movie editor we have, that can also control this camera for 
start/stop/capture etc, is kino. No other movie prosessing utility we 
have has ever been in the same county as a firewire port

Web submission site at aliexpress.com has no clue what to do with a a 
raw-dv file and refuses to take it as an evidence submission.

Kino, as in running on a fully uptodate wheezy, apparently can't find 
ffmpeg to make the conversion when I attempt to export this 1 minutes 
worth of raw-dv format video.  ffmpeg and all its friends are installed. 
But in kino, the whole page of mpeg4 options is ghosted out.

Does anybody have a clue what I should sniff about for next?

Thanks & Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



Re: SUCESS!!! - was [Re: Progress report Re: Invoking ddrescue]

2016-11-14 Thread Brian
On Mon 14 Nov 2016 at 16:29:52 -0600, Richard Owlett wrote:

> ddrescue has run to completion without _reported_ errors for all partitions
> of the drive. I understand that does *NOT* guarantee that the files are not
> corrupt.
> 
> I've read the man page of su with recent experiences in mind.
> I agree with tomas that some of my recent problems relate to the differences
> between "su" and "su --login".

tomas did not say he agreed that any of your recent problems relate
to the differences between "su" and "su --login". He explained the
difference between "su" and "su -", a factual matter.

Speaking of facts: we've had the appearance of subtle differences and
matching observed symptoms. Fuzzy. Nothing concrete and nothing that
doesn't involve speculation or possibly misobservation. As far as I am
concerned, all the commands used to carry out your task can be issued
successfully as root or after a su to root.

-- 
Brian.



Please take me off of your list

2016-11-14 Thread Ed Eastman
Thanks,
Ed Eastman



SUCESS!!! - was [Re: Progress report Re: Invoking ddrescue]

2016-11-14 Thread Richard Owlett
ddrescue has run to completion without _reported_ errors for all 
partitions of the drive. I understand that does *NOT* guarantee 
that the files are not corrupt.


I've read the man page of su with recent experiences in mind.
I agree with tomas that some of my recent problems relate to the 
differences between "su" and "su --login".




On 11/14/2016 1:09 PM, Richard Owlett wrote:

There is light at the end of the tunnel which doesn't appear to
be an oncoming train ;/

This is a manually created transcript of what I've done this
morning.
I physically can *NOT* do a copy-n-paste of what's happening as
it is
currently in progress on a separate _intentionally isolated_ laptop.

My procedure has been to login "root" at the Jessie boot screen.
I did *NOT* login as "richard" followed by executing "su" in a
terminal.
There *appears* to be subtle differences -- more investigation
needed.

A. Examine state of state of proposed target {/dev/sdb6} and the
defective
drive {dev/sdc} using Gparted
  I deleted existing but empty /dev/sdb6, created a new one
with an ext4
  file system labeled "recovered".
  The damaged drive shows as /dev/sdc partitioned as
  /dev/sdc1 ntfs  primary -- warning triangle and "---"
for used/unused space
  /dev/sdc2 fat32 primary -- displays reasonable values
for used/unused
  /dev/sdc3 extended
  /dev/sdc5 ntfs  logical -- displays reasonable values
for used/unused
  /dev/sdc6 ntfs  logical -- displays reasonable values
for used/unused
  /dev/sdc7 ntfs  logical -- displays reasonable values
for used/unused
B. Prepare the mount point
  mkdir /mnt/my_sdb6
C. Make it permanent by editing /etc/fstab by adding this line
  /dev/sdb6   /mnt/my_sdb6ext4rw  0   0
D. Mount it for the first time
  mount /mnt/my_sdb6
E. Attempt rescue with
ddrescue -p /dev/sdc1 /mnt/my_sdb6/my_sdc1 /mnt/my_sdb6/sdc1_log

The rescue appears to be progressing. ddrescue has been running
for 1/2 and reports rescuing ~47GB without any _reported_ errors.
That's unexpected as the partition was the Windows C: drive and
WinXP refused to boot. At the current rate I've another 2 hrs
minimum. I'm not concerned about the speed as both hard drive are
on USB2 ports.







Re: set domain name in Debian `

2016-11-14 Thread David Wright
On Mon 14 Nov 2016 at 08:27:06 (-0500), Greg Wooledge wrote:

> [...]   So when you do your "hostname -f"
> (which I still contend is a rubbish command which serves no useful
> purpose, but it's what you seem to want, so I'll roll with it), it
> looks up "srv" in this file as a whole word/field, and finds this line
> as the first match.
> 
> Therefore hostname -f writes "www.slsware.dmz" to stdout.

You asked earlier how we might even know about   hostname -f   and
the obvious answer is because exim emits:
"Starting MTA:hostname --fqdn did not return a fully qualified name,
dc_minimaldns will not work. Please fix your /etc/hosts setup."
if you have no domain name, but have   dc_minimaldns='true'   in
/etc/exim4/update-exim4.conf.conf

As your own   hostname -f   produces not dots, what approach do you
use to shut exim up, or do you just ignore (or suppress) the message?

Cheers,
David.



Re: Problema eliminando carpeta

2016-11-14 Thread divagante

On 11/11/16 22:01, alparkom wrote:




El 11/11/16 a las 21:58, Erick Ocrospoma escribió:



2016-11-11 18:53 GMT-05:00 alparkom >:




El 11/11/16 a las 20:20, fernando sainz escribió:

El día 11 de noviembre de 2016, 23:33, alparkom
> escribió:

Hola,

He estado intentando eliminar una carpeta y no he podido.
Me muestra el
error:

rm: no se puede borrar «path_dir»: El directorio no está
vacío

El comando que utilizo es:

rm -rf path_dir

También intenté con:

rmdir path_dir

Y lo mismo... además intenté moverlo a /tmp y me muestra
el mismo error.


Que puede ser? Vale.

Bueno, y has mirado que esté vació realmente, que no haya
ningún archivo oculto.
También podría ser que se estén usando acl's.

Intenté eliminarlo con el usuario root y aparecía el mismo error.
Y si hay archivos ocultos no debería poder eliminarse? Aunque
también ingresé a borrar todos los archivos manualmente.


S2.



​Es muy raro tu problema. Te has fijado los permisos que tiene? Si 
esta activado el sticky bit?
De hecho el directorio se creó como proyecto de Ionic, y las carpetas 
que no se eliminan tenían justamente ejecutables.

Te puedo recomendar que busques si dicha carpeta esta en uso:

$> lsof | grep path_dir

No esta en uso, de hecho puedo mover la carpeta.


lo otro, es que p​ruebes con algo asi: rm -Rf path_dir

Ya intenté, no me deja eliminarla.

Vale.





--


Erick.


---
IRC :   zerick
Blog: http://zerick.me
About : http://about.me/zerick
Linux User ID :  549567




Cierta vez me sucedio lo mismo..  o algo similar. Era un problema en el 
regido, si mal no recuerdo sectores defectuosos. Yo usaba el 
administrador de archivos Thunar y nada podia hacer. Creo que con 
Pcmanfm si pude (el administrador por defecto de lxde, instalable 
facilmente en cualquier entorno) y tambien otra vez lo logre con 
"ext2fs", una aplicacion o drivers para leer en windows sistemas de 
archivos ext.
 Por lo que contas me parece que el problema puede ser tu rigido y las 
suluciones las detalladas.


 Saludos


Re: A_Message_Regarding_Your_DEBT_Situation. vs78

2016-11-14 Thread Lisi Reisz
On Monday 14 November 2016 21:25:55 Jude DaShiell wrote:
> I sent the original message about debt situation to nobody, a criminal
> harvested my email address and is using it without authorization.

Obviously. :-)  I didn't even get the earlier messages - they got removed as 
SPAM I imagine. :-)  Unless this one from "Janet" IS the original message and 
is the spam.  And even that didn't reach me.  Yours, Jude, is the first to do 
so.

Lisi

> On Mon, 14 Nov 2016, Janet Platupe wrote:
> > Date: Mon, 14 Nov 2016 14:22:37
> > From: Janet Platupe 
> > To: Jude DaShiell , rhkra...@gmail.com,
> > debian-user@lists.debian.org
> > Subject: Re: A_Message_Regarding_Your_DEBT_Situation. vs78
> >
> > I AM NOT IN DEBT AND DO NOT OWE ANYTHING SO TO ME YOUR MESSAGE IS SPAM
> >
> > On Mon, Nov 14, 2016, 11:20 AM Jude DaShiell  wrote:
> >> asdg
> >>
> >>
> >>
> >>
> >>
> >> * Congratulation_janet: This_year,_let_GO_of_what_you_owe!
> >> Details_Inside *
> >>
> >> --
> >>
> >> Unsubscribe 
> >> ---
> >> UnsubscribeTounsubscribeplaesegohereorsendmailto:
> >> GRIFFIN'S_FLORAL_DESIGNS
> >> POBox29502 numb:91384
> >> LASVEGAS,NV 89126-9502
> >> UNITEDSTATES
> >>
> >> ClickHere 
> >>
> >>
> >> !$@%^%&*%^*%^
> >> 



Re: iptables question

2016-11-14 Thread Pascal Hambourg

Le 14/11/2016 à 00:48, deloptes a écrit :

Pascal Hambourg wrote:


Well then, all I can suggest is to run a packet capture and try to see
what's going on.


I guess  you mean on the firewall?


Yes.



Re: set domain name in Debian `

2016-11-14 Thread Glenn English

> On Nov 14, 2016, at 6:27 AM, Greg Wooledge  wrote:
> 
> On Sat, Nov 12, 2016 at 08:50:46AM -0700, Glenn English wrote:
>>> On Nov 12, 2016, at 3:25 AM, Andy Smith  wrote:
>>> I am 95% confident that the reason that Glenn's system thinks the
>>> FQDN is "www.slsware.dmz" is because the first instance of "srv" in
>>> the /etc/hosts is:
>>> 
> 192.168.2.203 www.slsware.dmz wsd srv

Who'da thunk it -- it's looking at the aliases in hosts, and grabbing the first 
one where the alias matches the hostname. If it sees any. I thought it was 
looking at IPs. But the way I had it set up, it wouldn't have worked that way 
either.

DNS wouldn't have worked either, if it's doing a reverse lookup. Not with this 
ghastly IP net I'm setting up -- there are several services on one server, so 
FTP and WWW both have the same IP. It would just do the first one, I suspect.

I rebooted with a perfectly good and unique IP and FQDN and an alias that 
didn't match the hostname, and it came up with an empty domain. I put in an 
alias (unique) the same as the hostname, and there was the domain. I didn't 
even have to reboot (Jessie, if it matters).

Thanks very much to all. This has been an educational experience. I guess I've 
been lucky with positioning for these 15 years.

I'm not going to toss hosts, though. I need to be able to move around the nets 
when DNS is down (or misconfigured). I'm just going to be a little bit more 
careful...

-- 
Glenn English




Re: A_Message_Regarding_Your_DEBT_Situation. vs78

2016-11-14 Thread Jude DaShiell
I sent the original message about debt situation to nobody, a criminal 
harvested my email address and is using it without authorization.


On Mon, 14 Nov 2016, Janet Platupe wrote:


Date: Mon, 14 Nov 2016 14:22:37
From: Janet Platupe 
To: Jude DaShiell , rhkra...@gmail.com,
debian-user@lists.debian.org
Subject: Re: A_Message_Regarding_Your_DEBT_Situation. vs78

I AM NOT IN DEBT AND DO NOT OWE ANYTHING SO TO ME YOUR MESSAGE IS SPAM

On Mon, Nov 14, 2016, 11:20 AM Jude DaShiell  wrote:


asdg





* Congratulation_janet: This_year,_let_GO_of_what_you_owe! Details_Inside
*

--

Unsubscribe 
---
UnsubscribeTounsubscribeplaesegohereorsendmailto:
GRIFFIN'S_FLORAL_DESIGNS
POBox29502 numb:91384
LASVEGAS,NV 89126-9502
UNITEDSTATES

ClickHere 


!$@%^%&*%^*%^





--



Re: Progress report Re: Invoking ddrescue

2016-11-14 Thread Richard Owlett

On 11/14/2016 2:27 PM, to...@tuxteam.de wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Nov 14, 2016 at 01:09:51PM -0600, Richard Owlett wrote:

There is light at the end of the tunnel which doesn't appear to be
an oncoming train ;/

This is a manually created transcript of what I've done this morning.
I physically can *NOT* do a copy-n-paste of what's happening as it is
currently in progress on a separate _intentionally isolated_ laptop.

My procedure has been to login "root" at the Jessie boot screen.
I did *NOT* login as "richard" followed by executing "su" in a
terminal.
There *appears* to be subtle differences -- more investigation
needed.


There is. If you invoke just "su", you inherit (more or less) the
(regular) user's environment, with some exceptions. If you invoke
"su -" (or equivalently "su -l") you get a fresh environment for
root, as if you had logged in as root directly.


My observed symptoms would seem to match.
I have a test case in mind that could verify that.
It will have to wait. I have a higher priority project thirsting 
for an available 300GB drive. It is the motivation for a lot of 
my recent posts ;/




The gory details are in su's man page (a bit complicated by the
fact that su can do more things, e.g. su'ing to another user instead
of root, executing just one command as the new user, and so on).

Jonathan commented on the other points much better than I could,
so I'll stop here :-)

regards
- -- tomás





Re: Progress report Re: Invoking ddrescue

2016-11-14 Thread Richard Owlett

On 11/14/2016 2:23 PM, Thomas Schmitt wrote:

Hi,

Richard Owlett wrote:

  /dev/sdc3 extended


This one does not need to be copied because it is a container around
the "logical" partitions sd5, sdc6, sdc7.




Back in the day I was involved in QA/QC and bailing out our field 
service people






ddrescue has been running for 1/2 and
reports rescuing ~47GB without any _reported_ errors. That's unexpected as
the partition was the Windows C: drive and WinXP refused to boot.


Do you get any specific messages from the boot refusal ?
Like bad disk or so ?


No way to know at this late date. I has not been in a computer 
for over a year, possibly 2.


Trouble shooting the drive has been on my "to do" list. Right now 
I could use another 300GB of free (as in beer) storage. I have no 
need of another Windows machine.




If the computer has EFI boot firmware, if it is in non-legacy mode, and if
dev/sdc2 is reported by e.g. /sbin/fdisk -l as type "EFI (FAT-12/16/32)",
then booting starts there.

If the computer has old BIOS or EFI in legacy mode, then booting starts
at block 0 of the base device /dev/sdc. Normally the first partition starts
not there but rather 31 to 2048 blocks later.


Have a nice day :)

Thomas






Re: Progress report Re: Invoking ddrescue

2016-11-14 Thread Richard Owlett

On 11/14/2016 2:16 PM, Jonathan Dowland wrote:

On Mon, Nov 14, 2016 at 01:09:51PM -0600, Richard Owlett wrote:

There is light at the end of the tunnel which doesn't appear to be an
oncoming train ;/

This is a manually created transcript of what I've done this morning.
I physically can *NOT* do a copy-n-paste of what's happening as it is
currently in progress on a separate _intentionally isolated_ laptop.


Broadly the transcript looks fine to me.


The rescue appears to be progressing. ddrescue has been running for 1/2 and
reports rescuing ~47GB without any _reported_ errors. That's unexpected as
the partition was the Windows C: drive and WinXP refused to boot.


It's possible that WinXP has corrupted files, or a corrupted filesystem, on top
of a perfectly fine drive. This can happen for any number of reasons, including
unexpected power cuts whilst Win XP was applying an update of some sort and in
the middle of writing a critical file.

Whilst ddrescue is running, you could, if you wish, check the drive's S.M.A.R.T.
(Self-Monitoring, Analysis and Reporting Technology) logs, if you have smartctl
(from the smartmontools package) installed. The command (as root/superuser) is

smartctl -a /dev/sdc

This *should* not have any impact whatsoever on the running ddrescue. The output
is quite long so you may wish to pipe the above command to a pager (such as 
less)
by appending "| less", and/or capture the output to another file (achieved at 
the
same time by piping to 'tee' first, e.g. | tee -a some-output-file | less)

The output might include lines such as the following  (all taken from running 
the
command on one of my HDDs):

...

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

...

SMART Error Log Version: 1
No Errors Logged

...

The output (in particular the "Vendor Specific SMART Attributes with 
Thresholds")
can be hard to interpret, which is why I suggested also saving to a file, but
would tell you if the drive itself thinks it has suffered a failure.

However if you are very risk-averse you are probably best leaving the machine
entirely until ddrescue is complete.

(definitely for another time: you can also instruct drives which support 
S.M.A.R.T.
to perform one of a number of self-tests for problems using smartctl)


At the current rate I've another 2 hrs minimum. I'm not concerned about the
speed as both hard drive are on USB2 ports.


It can take a very long time, especially once it gets to the later stages
(scraping, trims, retries, etc.)

I've been reading a single damaged DVD-r (capacity ~4GiB) for over a week and
I'm not finished (I have interrupted the process however, as I am about to a
different optical drive, which can be helpful when recovering from optical media
but this is not relevant to HDDs or your situation)



I think I may go with the idea of corrupted file contents which 
create meaningless content that can be reliably read. I still 
have no _reported_ errors although the "current rate:" 
occasionally drops to ~3% of "average rate:". I don't know how 
hard WinXP tries to read marginal sectors.


In this case, I am significantly "very risk-averse" ;/ It is 
running. I will leave well enough alone.




Re: [COLABORAÇÃO]: Monitoramento de ambiente com Centreon

2016-11-14 Thread Thiago Gomes
qual é a diferença entre ele e o zabbix ?

Em 14 de novembro de 2016 17:14, Sinval Júnior  escreveu:
> Colaboração, ou Publicidade?
>
> Ao encaminhar esta mensagem, por favor:
> 1 - Apague meu endereço eletrônico;
> 2 - Encaminhe como Cópia Oculta (Cco ou BCc) aos seus destinatários.
> Dificulte assim a disseminação de vírus, spams e banners.
>
> #=+
> #!/usr/bin/env python
> nome = 'Sinval Júnior'
> email = 'sinvalju arroba gmail ponto com'
> print nome
> print email
> #==+
>
> 2016-11-10 19:54 GMT-02:00 Henrique Fagundes :
>>
>> Prezados colegas,
>>
>> Gostaria de colaborar com a comunidade, fazendo uma explanação sobre o
>> Centreon:
>>
>> Segue o link:
>> https://www.aprendendolinux.com/monitoramento-de-ambiente-com-centreon/
>>
>> Espero que seja útil para alguém.
>>
>> Atenciosamente,
>>
>> Henrique Fagundes
>> henri...@linuxadmin.com.br
>> Skype: magnata-br-rj
>> Linux User: 475399
>>
>> http://www.aprendendolinux.com/
>> http://www.facebook.com/PortalAprendendoLinux
>> http://youtube.com/aprendendolinux/
>> http://twitter.com/aprendendolinux/
>> __
>> Participe do Grupo Aprendendo Linux
>> http://listas.aprendendolinux.com
>>
>> Ou envie um e-mail para:
>> aprendendolinux-subscr...@listas.aprendendolinux.com
>>
>



-- 
Thiago Gomes



Re: Progress report Re: Invoking ddrescue

2016-11-14 Thread tomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Nov 14, 2016 at 01:09:51PM -0600, Richard Owlett wrote:
> There is light at the end of the tunnel which doesn't appear to be
> an oncoming train ;/
> 
> This is a manually created transcript of what I've done this morning.
> I physically can *NOT* do a copy-n-paste of what's happening as it is
> currently in progress on a separate _intentionally isolated_ laptop.
> 
> My procedure has been to login "root" at the Jessie boot screen.
> I did *NOT* login as "richard" followed by executing "su" in a
> terminal.
> There *appears* to be subtle differences -- more investigation
> needed.

There is. If you invoke just "su", you inherit (more or less) the
(regular) user's environment, with some exceptions. If you invoke
"su -" (or equivalently "su -l") you get a fresh environment for
root, as if you had logged in as root directly.

The gory details are in su's man page (a bit complicated by the
fact that su can do more things, e.g. su'ing to another user instead
of root, executing just one command as the new user, and so on).

Jonathan commented on the other points much better than I could,
so I'll stop here :-)

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlgqHj4ACgkQBcgs9XrR2kZyzwCfUtGS2LOYMjSZPiKpXjjVlVVe
Fm8AniuuM5RYsEqJoz7Y7LDEePn5OBeR
=DY4U
-END PGP SIGNATURE-



Re: Progress report Re: Invoking ddrescue

2016-11-14 Thread Thomas Schmitt
Hi,

Richard Owlett wrote:
>  /dev/sdc3 extended

This one does not need to be copied because it is a container around
the "logical" partitions sd5, sdc6, sdc7.


> ddrescue has been running for 1/2 and
> reports rescuing ~47GB without any _reported_ errors. That's unexpected as
> the partition was the Windows C: drive and WinXP refused to boot.

Do you get any specific messages from the boot refusal ?
Like bad disk or so ?

If the computer has EFI boot firmware, if it is in non-legacy mode, and if
dev/sdc2 is reported by e.g. /sbin/fdisk -l as type "EFI (FAT-12/16/32)",
then booting starts there.

If the computer has old BIOS or EFI in legacy mode, then booting starts
at block 0 of the base device /dev/sdc. Normally the first partition starts
not there but rather 31 to 2048 blocks later.


Have a nice day :)

Thomas



Re: Progress report Re: Invoking ddrescue

2016-11-14 Thread Jonathan Dowland
On Mon, Nov 14, 2016 at 01:09:51PM -0600, Richard Owlett wrote:
> There is light at the end of the tunnel which doesn't appear to be an
> oncoming train ;/
> 
> This is a manually created transcript of what I've done this morning.
> I physically can *NOT* do a copy-n-paste of what's happening as it is
> currently in progress on a separate _intentionally isolated_ laptop.

Broadly the transcript looks fine to me.

> The rescue appears to be progressing. ddrescue has been running for 1/2 and
> reports rescuing ~47GB without any _reported_ errors. That's unexpected as
> the partition was the Windows C: drive and WinXP refused to boot.

It's possible that WinXP has corrupted files, or a corrupted filesystem, on top
of a perfectly fine drive. This can happen for any number of reasons, including
unexpected power cuts whilst Win XP was applying an update of some sort and in
the middle of writing a critical file.

Whilst ddrescue is running, you could, if you wish, check the drive's S.M.A.R.T.
(Self-Monitoring, Analysis and Reporting Technology) logs, if you have smartctl
(from the smartmontools package) installed. The command (as root/superuser) is

smartctl -a /dev/sdc

This *should* not have any impact whatsoever on the running ddrescue. The output
is quite long so you may wish to pipe the above command to a pager (such as 
less)
by appending "| less", and/or capture the output to another file (achieved at 
the
same time by piping to 'tee' first, e.g. | tee -a some-output-file | less)

The output might include lines such as the following  (all taken from running 
the
command on one of my HDDs):

...
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
...
> SMART Error Log Version: 1
> No Errors Logged
...

The output (in particular the "Vendor Specific SMART Attributes with 
Thresholds")
can be hard to interpret, which is why I suggested also saving to a file, but
would tell you if the drive itself thinks it has suffered a failure.

However if you are very risk-averse you are probably best leaving the machine
entirely until ddrescue is complete.

(definitely for another time: you can also instruct drives which support 
S.M.A.R.T.
to perform one of a number of self-tests for problems using smartctl)

> At the current rate I've another 2 hrs minimum. I'm not concerned about the
> speed as both hard drive are on USB2 ports.

It can take a very long time, especially once it gets to the later stages
(scraping, trims, retries, etc.)

I've been reading a single damaged DVD-r (capacity ~4GiB) for over a week and
I'm not finished (I have interrupted the process however, as I am about to a 
different optical drive, which can be helpful when recovering from optical media
but this is not relevant to HDDs or your situation)

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature


Re: [COLABORAÇÃO]: Monitoramento de ambiente com Centreon

2016-11-14 Thread Sinval Júnior
Colaboração, ou Publicidade?

Ao encaminhar esta mensagem, por favor:
1 - Apague meu endereço eletrônico;
2 - Encaminhe como Cópia Oculta (Cco ou BCc) aos seus destinatários.
Dificulte assim a disseminação de vírus, spams e banners.

#=+
#!/usr/bin/env python
nome = 'Sinval Júnior'
email = 'sinvalju arroba gmail ponto com'
print nome
print email
#==+

2016-11-10 19:54 GMT-02:00 Henrique Fagundes :

> Prezados colegas,
>
> Gostaria de colaborar com a comunidade, fazendo uma explanação sobre o
> Centreon:
>
> Segue o link:
> https://www.aprendendolinux.com/monitoramento-de-ambiente-com-centreon/
>
> Espero que seja útil para alguém.
>
> Atenciosamente,
>
> Henrique Fagundes
> henri...@linuxadmin.com.br
> Skype: magnata-br-rj
> Linux User: 475399
>
> http://www.aprendendolinux.com/
> http://www.facebook.com/PortalAprendendoLinux
> http://youtube.com/aprendendolinux/
> http://twitter.com/aprendendolinux/
> __
> Participe do Grupo Aprendendo Linux
> http://listas.aprendendolinux.com
>
> Ou envie um e-mail para:
> aprendendolinux-subscr...@listas.aprendendolinux.com
>
>


Vivaldi & apt-get?

2016-11-14 Thread John Conover

When updating vivaldi in Wheezy 7.X, I get "The following packages
have been kept back" vivaldi-stable.

Vivaldi updates fine in Jessie 8.X.

Both were i386, (32 bit,) installed via ".deb" files.

How do I fix Wheezy?

Thanks,

John

-- 

John Conover, cono...@rahul.net, http://www.johncon.com/



Re: iptables question

2016-11-14 Thread deloptes
Henning Follmann wrote:

> Last time I chime in here.
> I understand growth and chaos, believe me. However sometimes we need a
> nudge or a kick in the but to clean up. Maybe this is your call..

It is kicking me and calling me since some time but I can not do this before
next summer. I have to sit there with RS232 cable to be able to do the
testing and repair if something fails. Perhaps I have luck and I can do it
earlier, but not very likely.

> Simplicity is a beautiful thing my friend

yes indeed - as I mentioned I did not write this and I don'T know why the
guy who wrote it, did it that way.

regards




Progress report Re: Invoking ddrescue

2016-11-14 Thread Richard Owlett
There is light at the end of the tunnel which doesn't appear to 
be an oncoming train ;/


This is a manually created transcript of what I've done this morning.
I physically can *NOT* do a copy-n-paste of what's happening as it is
currently in progress on a separate _intentionally isolated_ laptop.

My procedure has been to login "root" at the Jessie boot screen.
I did *NOT* login as "richard" followed by executing "su" in a 
terminal.
There *appears* to be subtle differences -- more investigation 
needed.


A. Examine state of state of proposed target {/dev/sdb6} and the 
defective

   drive {dev/sdc} using Gparted
 I deleted existing but empty /dev/sdb6, created a new one 
with an ext4

 file system labeled "recovered".
 The damaged drive shows as /dev/sdc partitioned as
 /dev/sdc1 ntfs  primary -- warning triangle and "---" 
for used/unused space
 /dev/sdc2 fat32 primary -- displays reasonable values 
for used/unused

 /dev/sdc3 extended
 /dev/sdc5 ntfs  logical -- displays reasonable values 
for used/unused
 /dev/sdc6 ntfs  logical -- displays reasonable values 
for used/unused
 /dev/sdc7 ntfs  logical -- displays reasonable values 
for used/unused

B. Prepare the mount point
 mkdir /mnt/my_sdb6
C. Make it permanent by editing /etc/fstab by adding this line
 /dev/sdb6   /mnt/my_sdb6ext4rw  0   0
D. Mount it for the first time
 mount /mnt/my_sdb6
E. Attempt rescue with
   ddrescue -p /dev/sdc1 /mnt/my_sdb6/my_sdc1 /mnt/my_sdb6/sdc1_log

The rescue appears to be progressing. ddrescue has been running 
for 1/2 and reports rescuing ~47GB without any _reported_ errors. 
That's unexpected as the partition was the Windows C: drive and 
WinXP refused to boot. At the current rate I've another 2 hrs 
minimum. I'm not concerned about the speed as both hard drive are 
on USB2 ports.





Re: apt-get fails to install pylint3

2016-11-14 Thread janm
Hi Tony

What if you tell APT specifically to use Backports via "-t jessie-backports"? 
Please see my simulation install below.

Kind regards

Jan

sudo apt-get install -t jessie-backports pylint3 -s -V
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
   blt (2.5.3+dfsg-1)
   libtcl8.6 (8.6.2+dfsg-2)
   libtk8.6 (8.6.2-1)
   python3-astroid (1.4.4-1~bpo8+1)
   python3-lazy-object-proxy (1.2.1-1~bpo8+1)
   python3-logilab-common (1.1.0-1~bpo8+1)
   python3-tk (3.4.2-1+b1)
   python3-wrapt (1.8.0-5)
   tk8.6-blt2.5 (2.5.3+dfsg-1)
Suggested packages:
   blt-demo (2.5.3+dfsg-1)
   tcl8.6 (8.6.2+dfsg-2)
   tk8.6 (8.6.2-1)
   pylint-doc (1.5.2-1~bpo8+1)
   tix (8.4.3-7~bpo8+1)
   python3-tk-dbg (3.4.2-1+b1)
The following NEW packages will be installed:
   blt (2.5.3+dfsg-1)
   libtcl8.6 (8.6.2+dfsg-2)
   libtk8.6 (8.6.2-1)
   pylint3 (1.5.2-1~bpo8+1)
   python3-astroid (1.4.4-1~bpo8+1)
   python3-lazy-object-proxy (1.2.1-1~bpo8+1)
   python3-logilab-common (1.1.0-1~bpo8+1)
   python3-tk (3.4.2-1+b1)
   python3-wrapt (1.8.0-5)
   tk8.6-blt2.5 (2.5.3+dfsg-1)
0 upgraded, 10 newly installed, 0 to remove and 168 not upgraded.


On Mon Nov 14, 2016 at 16:14:33, Tony van der Hoff wrote:
> Hi,
> 
> I'm trying to install pylint3 on my jessie system.
> According to synaptic, pylint3 is available from backports, which I've
> enabled in sources.list. However, it depends on python3-astroid, which it
> refused to install:
> 
> #
> tony@tony-lx:~$ sudo apt-get install pylint3
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  pylint3 : Depends: python3-astroid (>= 1.4.1) but 1.2.1-3 is to be
> installed
> E: Unable to correct problems, you have held broken packages.
> #
> 
> Has anyone got any suggestions?
> -- 
> Tony van der Hoff| mailto:t...@vanderhoff.org
> Buckinghamshire, England |
> 



Re: [Aptitude-devel] aptitude ~A question

2016-11-14 Thread David Wright
On Mon 14 Nov 2016 at 14:05:46 (+0100), steve wrote:
> Hi David,
> 
> Coming back to this problem now that I have a bit more time.
> 
> As I have been making a lot of testing, this message is a bit long,
> sorry for that.
> 
> 
> >If you follow my recipe, any packages counted twice (as eg in both
> >the stable and jessie searches) will show up in the diff with a "-".
> 
> I have done this first for a = [trusty,jessie$,jessie-backports,stable]
> and then for a = now. No output for jessie$.
> 
> Then I have done this:
> 
> cat jessie-backports.txt trusty.txt stable.txt | sort | diff -u -now.txt > 
> diff.txt
> 
> The first lines of diff.txt show
[snipped]
> Now, for example, we see that autopoint is present twice (once with a
> "-" and once with a blank space at the beginning of the line). So if I
> understand correctly, the package "autopoint" appears once in both the
> concatenation and in the total file and another time only in the
> concatenation. Can I see this behaviour using apt-cache?
> 
> apt-cache policy autopoint autopoint:
>  Installé : 0.19.3-2
>  Candidat : 0.19.3-2
> Table de version :
> 0.19.8.1-1~bpo8+1 0
>100 http://ftp.ch.debian.org/debian/ jessie-backports/main amd64 
> Packages
> *** 0.19.3-2 0
>500 http://ftp.ch.debian.org/debian/ jessie/main amd64 Packages
>100 /var/lib/dpkg/status
> 
> 
> So it seems that it's the jessie version which is installed. But
> 
> aptitude search ~Astable~i | grep autopoint
> i A autopoint
> 
> aptitude search ~Ajessie$~i | grep autopoint
> (no output)
> 
> aptitude search ~Ajessie-backports~i | grep autopoint
> i A autopoint
> 
> 
> which contradicts apt-cache! Is this a bug? Same behaviour for the
> package cmake-data.

I'm glad this method is shining a light on your problem. I'm afraid
that I'm not very experienced in running the many apt* commands
available, but others may help.

> (BTW, this package is taken from jessie but there is an existing
> backport package. Is is possible to upgrade to jessie-backports all
> jessie packages which have a jessie-backports version?)

One *might* try the brute force approach of just telling it to reinstall
everything on your system, but specifying -t jessie-backports as the
target, and -s of course to prevent anything happening while you checked.
But I don't know the answer.

Cheers,
David.



Re: Layers for the package manager

2016-11-14 Thread Jonathan Dowland
On Sat, Nov 12, 2016 at 09:18:26PM +0100, Nicolas George wrote:
> If I understand correctly how Docker works, its images are big blobs
> that contain the program they are meant to distribute plus all its
> dependencies. Am I mistaken?

That's broadly true, at least, they are presented to the user that way.

> If it works like that, that means when the next OpenSSL security issue
> is found, we have to cross our fingers very tightly and hope whoever
> released the image will release an update with a fixed library. 

If the dockerized application you were using did not use OpenSSL, you don't
need to do anything.

If it does, then it needs to be rebuilt.

As a user, you could wait for the image author to rebuild it, then pull the
newer version. It's quite likely the image author based their image on top of
another, and that the parent image (or a parent image somewhere up the chain)
is the "owner" of the problem. For example, if the image you were using had
been built on top of the "debian" image, the image author would have to wait
until the author/owner of the "debian" image updated, first. (Note: that isn't
the Debian project, confusingly!)

This is pretty bad.

Another option is, you create a new derivative image yourself, which is
built on top of the application image you were using, and updates OpenSSL.
That would be roughly as simple as a Dockerfile with two instructions

FROM some-application-image
RUN apt-get update && apt-get upgrade -y

(the above fed to "docker build -t my-new-image-name ")

The abstraction is already a bit broken though, because you need to know
that the image was based on a Debian-like OS; that OS needs to have updated
the OpenSSL library; the application has to continue to function with the
new library version (and that might not be tested yet)

And none of the above is automatic.

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature


Re: How to run a script before shutdown?

2016-11-14 Thread Robert Latest
Hi Sven,

thanks, that's 99% of what I need (I'd found that thread before but didn't
really read it all the way because it looked like discussion going
nowhere). It still needs some tweaking, though, because it runs the backup
script whenever multiuser mode is left -- no matter if it's a shutdown or
reboot. In practise this doesn't make any significant difference though.

Regards,
robert

On Sun, Nov 13, 2016 at 9:26 PM, Sven Joachim  wrote:

> On 2016-11-13 20:34 +0100, Robert Latest wrote:
>
> > I want to automatically start a data backup script (to USB or network
> > drive) at each shutdown of my computer. I did some research into this
> > and found that several people have the same problem as I do. But the
> > threads I found petered out into discussions of several ways of doing
> > this, working for some people and not for others.  So here I am
> > wondering if there is a canonical, proper and reliable method of doing
> > this.
> >
> > The script needs to run when a shutdown (but not a reboot) is started
> > while networking and USB mounts are still up, and (preferably)
> > multi-user mode has turned off. Perusing the systemd documentation I
> > found all kinds of good examples of how to start stuff in a well-ordered
> > manner to get the system up, but for shutting down there is quite little
> > information.
> >
> > How is it done?
>
> There is a possible answer on superuser.com[1], scroll towards the end.
>
> HTH,
> Sven
>
>
> 1. http://superuser.com/questions/1016827/how-do-i-run-a-script-before-
> everything-else-on-shutdown-with-systemd
>
>


Re: Two Chromebooks: was Re: LENOVO IdeaPad 100S 11.6" Laptop

2016-11-14 Thread Michael Lange
On Sun, 13 Nov 2016 01:27:57 +0100
Michael Lange  wrote:

> On Sat, 12 Nov 2016 23:51:46 +
> Lisi Reisz  wrote:
> 
> > I don't mind about having to struggle
> > a little, and Bluetooth doesn't worry me, but sound is a bit of a
> > killer. 
> 
> I just looked again at
> https://bugzilla.kernel.org/show_bug.cgi?id=117141 where the sound
> issue is being discussed, there is now a link pointing to
> https://github.com/torvalds/linux/commit/a68bc0d43e1b96c374c4b03eb9baa662778357b3#diff-ad362ef9a62cab4653b68cafab76824b
> which may or may not fix the sound problems with kernel 4.9, I think
> I'll try this out one of these days.

Ok, just for the record: tried kernel 4.9.0, still no sound with the
Ideapad 100S.


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

"Life and death are seldom logical."
"But attaining a desired goal always is."
-- McCoy and Spock, "The Galileo Seven", stardate 2821.7



Re: apt-get fails to install pylint3

2016-11-14 Thread Tony van der Hoff

On 14/11/16 16:45, janm wrote:

Hi Tony

What if you tell APT specifically to use Backports via "-t jessie-backports"? 
Please see my simulation install below.



Thank you, Jan; that seems to have worked.

Best regards, Tony


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



Re: How to run a script before shutdown?

2016-11-14 Thread rhkramer
Good point--thanks for the correction!

On Monday, November 14, 2016 10:26:04 AM Jude DaShiell wrote:
> After a script starts, each command in that script runs until the script
> ends.  I noticed when doing something different with wget and wanting to
> have wget do one command then wait until a download had completed that
> without a read command somewhere in the script the next wget command
> fires off as soon as the first one runs.
> 
> On Mon, 14 Nov 2016, rhkra...@gmail.com wrote:
> > Date: Mon, 14 Nov 2016 07:33:19
> > From: rhkra...@gmail.com
> > To: debian-user@lists.debian.org
> > Subject: Re: How to run a script before shutdown?
> > Resent-Date: Mon, 14 Nov 2016 12:33:40 + (UTC)
> > Resent-From: debian-user@lists.debian.org
> > 
> > On Sunday, November 13, 2016 08:29:46 PM David Christensen wrote:
> >> On 11/13/2016 11:34 AM, Robert Latest wrote:
> >>> I want to automatically start a data backup script (to USB or network
> >>> drive) at each shutdown of my computer.
> >> 
> >> Rather than having the system call my backup/ archive scripts, I have my
> >> backup/ archive scripts call 'shutdown' when they're done.
> > 
> > I'm not the OP, but, wonderful idea!  And, of course, I can pass a
> > parameter to my backup script--one case to shutdown after the backup,
> > and one not to shutdown!



Re: apt-get fails to install pylint3

2016-11-14 Thread Henning Follmann
On Mon, Nov 14, 2016 at 04:14:33PM +, Tony van der Hoff wrote:
> Hi,
> 
> I'm trying to install pylint3 on my jessie system.
> According to synaptic, pylint3 is available from backports, which I've
> enabled in sources.list. However, it depends on python3-astroid, which it
> refused to install:
> 
> #
> tony@tony-lx:~$ sudo apt-get install pylint3
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  pylint3 : Depends: python3-astroid (>= 1.4.1) but 1.2.1-3 is to be
> installed
> E: Unable to correct problems, you have held broken packages.
> #
> 
> Has anyone got any suggestions?

Sure, install a newer version of python3-astroid.
It says so in the error message.
I guess you have an older package installed before you added the backports
to your repository.

-H



-- 
Henning Follmann   | hfollm...@itcfollmann.com



apt-get fails to install pylint3

2016-11-14 Thread Tony van der Hoff

Hi,

I'm trying to install pylint3 on my jessie system.
According to synaptic, pylint3 is available from backports, which I've 
enabled in sources.list. However, it depends on python3-astroid, which 
it refused to install:


#
tony@tony-lx:~$ sudo apt-get install pylint3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 pylint3 : Depends: python3-astroid (>= 1.4.1) but 1.2.1-3 is to be 
installed

E: Unable to correct problems, you have held broken packages.
#

Has anyone got any suggestions?
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |



Re: How to run a script before shutdown?

2016-11-14 Thread Jude DaShiell
After a script starts, each command in that script runs until the script 
ends.  I noticed when doing something different with wget and wanting to 
have wget do one command then wait until a download had completed that 
without a read command somewhere in the script the next wget command 
fires off as soon as the first one runs.


On Mon, 14 Nov 2016, rhkra...@gmail.com wrote:


Date: Mon, 14 Nov 2016 07:33:19
From: rhkra...@gmail.com
To: debian-user@lists.debian.org
Subject: Re: How to run a script before shutdown?
Resent-Date: Mon, 14 Nov 2016 12:33:40 + (UTC)
Resent-From: debian-user@lists.debian.org

On Sunday, November 13, 2016 08:29:46 PM David Christensen wrote:

On 11/13/2016 11:34 AM, Robert Latest wrote:

I want to automatically start a data backup script (to USB or network
drive) at each shutdown of my computer.


Rather than having the system call my backup/ archive scripts, I have my
backup/ archive scripts call 'shutdown' when they're done.


I'm not the OP, but, wonderful idea!  And, of course, I can pass a parameter
to my backup script--one case to shutdown after the backup, and one not to
shutdown!




--



Re: Does hdparm not run at startup anymore?

2016-11-14 Thread Cindy-Sue Causey
On 11/12/16, Rainer Dorsch  wrote:
>
> On Saturday 12 November 2016 16:40:40 Alex Mestiashvili wrote:
>> On 11/12/2016 08:37 AM, Rainer Dorsch wrote:
>> > + Alexandre, hdparm maintainer
>> >
>> > On Friday 11 November 2016 23:11:24 Rainer Dorsch wrote:
>> >> Hi,
>> >>
>> >> I configure sdb in /etc/hdparm.conf to apm=64, but when I start the
>> >> system, apm does not change. Interesting enough a /etc/init.d/hdparm
>> >> restart fixes the problem:
>> >>
>> >> < snipped for brevity >
>> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>> >> Advanced power management level: 254
>> >> root@Silberkiste:~# /etc/init.d/hdparm restart
>> >> [ ok ] Restarting hdparm (via systemctl): hdparm.service.
>> >> root@Silberkiste:~# hdparm -I /dev/sdb|grep level
>> >> Advanced power management level: 64
>> >> root@Silberkiste:~#
>> >>
>> >>
>> >> Any insight, why I need the /etc/init.d/hdparm restart is very
>> >> welcome.
>> >>
>> >>
>> Hi Rainer,
>> I can not reproduce this problem on my machine:
>>
>> lsb_release -c
>> Codename:jessie
>>
>> hdparm -V
>> hdparm v9.43
>>
>> < snipped for brevity >
>
> Hmm...since hdparm works for me if I do a
>
> # /etc/init.d/hdparm restart
>
> after boot (or even in /etc/rc.local, is it possible that hdparm runs for my
> system for whatever reason too early (though it is not special setup, all
> SATA SSDs and HDDs)?


Hi.. Have CC'd those recently brought into the loop (because it seemed
the proper thing to do)..

What I'm sharing is "similarly different". It's only one of the
problems I'm having with (STILL) attempting to get wireless/Bluetooth
to function, but this thread right here is one of the things I'm
facing, too.

It's been a few days since I... attempted it so I've forgotten which
[package] this worked for, but one function that WAS working needed a
manual restart after reboots. Whichever [package] it was, that package
would be "failed" (or similar error) for a "systemctl status" command
issuance. It would then function fine (based on systemctl status query
feedback) after a "systemctl restart" terminal command line restart.
Again, this was all immediately after a fresh reboot where things
become reset.

Been a couple threads recently where my instance seemed to potentially
apply, as well, actually. Like maybe it's hinting at something more
universal involved beyond singular packages. I'm on Sid Unstable
(attempting a Stretch debootstrap in just a few).

Cindy :)

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

* Ya gotta find your crochet-t-t-t-t!!! *



Re: wheezy, cannot change the address of eth1

2016-11-14 Thread Gene Heskett
On Monday 14 November 2016 08:38:24 Greg Wooledge wrote:

> Others have already pointed this out, but you have two conflicting
> "gateway" lines, on two completely separate networks.  You need to
> pick one.

As it turned out, bringing up an eth0:1 was the answer. It also appears 
that its default configuration seems to do exactly what I wanted it to 
do, which is to act as a hub, expanding the number of ports available by 
enabling another 8 ports in the garage on the end of that cable, and 
reducing by about 150 feet, the length of cable and a simple hub it 
presently travels thru to get 10 feet physically.

I had, with extreme difficulty, fished a piece of cat5e thru a largely 
in-accessable piece of this structure called a house, in order to get 
the network to the G0704. And I've enough jumper cables so that it, the 
r-pi, o-pi and an old dell it appears I will have to use as an X 
renderer for the r-pi's output, can all be plugged in at the same time.

I was going to use the o-pi for that, but its hdmi port is defective. So 
job one this morning is to take my movie camera out and takes a short 
film of it booting the oem os, then booting armbian, and sending that 
back to the vendor to prove its display hdwe is defective.  Its color 
alright, a mixture of pale lime green in the highlights, with a burple 
overlay over everything, extremely poor experience for these old eyes.  
Insulting even. The display from the r-pi, using the same cable and 
dvd-i adapter, is pure and perfect.

If alibaba will replace the o-pi, I might still try to use it, next 
summer maybe when I need to get rid of the Dells heat.  But till then 
the old p4 Dell will have to do.

So I will pick a path and just do it instead of wasting time discussing 
it. :)

Cheers Greg, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 



Re: how to make vlc to default videoplayer in gnome

2016-11-14 Thread Fekete Tamás
Hello!

It works now.
Thank you Henning, and thanks for the other answer too.

- Tamas Fekete

2016-11-10 14:33 GMT+01:00 Alexandre GRIVEAUX :

> Hello,
>
> A easy fix:
>
> Try a right click on the files you want to open, select tab 'open with'
> and choose VLC
>
>
>
> Le 10/11/2016 à 12:40, Fekete Tamás a écrit :
> > Dear all,
> >
> > I have problems with setting up the default video player program in
> GNOME.
> >
> > I tried to vi /etc/gnome/defaults.list as root.
> >
> > I modified a line first like this:
> > video/flv=vlc.Totem
> >
> > I quit from my gnome session, than started the X again.
> >
> > The default app still wasn't vlc, so I tried to edit
> > /etc/gnome/defaults.list like this:
> > video/flv=vlc.Totem.desktop
> >
> > A repeated the gnome restart procedure, but the default player still
> > hasn't change.
> >
> > Can anyone help me, what is the correct text has to be in
> > defaults.list to make vlc to my default player?
> > Or is there any other file I have to modify?
> >
> > I use debian 8.6 amd64 version which is upgraded from debian 8.5
> >
> > - Tamas Fekete
> >
>
>


Re: wheezy, cannot change the address of eth1

2016-11-14 Thread Greg Wooledge
> > Start by showing the contents of /etc/network/interfaces.

On Fri, Nov 11, 2016 at 07:59:01PM -0500, Gene Heskett wrote:
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> auto lo
> 
> # The loopback network interface
> iface lo inet loopback
> address 127.0.0.1
> netmask 255.255.255.0
> 
> auto eth0
> 
> # regular network for coyote.den
> iface eth0 inet static
> address 192.168.71.3
> netmask 255.255.255.0
> gateway 192.168.71.1
> 
> auto eth1
> 
> # to access reset to 192.168.0.1 routers/switches on the 2nd cat5 port
> iface eth1 inet static
> address 192.168.0.25
> netmask 255.255.255.0
> gateway 192.168.0.1

Others have already pointed this out, but you have two conflicting
"gateway" lines, on two completely separate networks.  You need to
pick one.



Re: set domain name in Debian `

2016-11-14 Thread Greg Wooledge
On Sat, Nov 12, 2016 at 08:50:46AM -0700, Glenn English wrote:
> > On Nov 12, 2016, at 3:25 AM, Andy Smith  wrote:
> > I am 95% confident that the reason that Glenn's system thinks the
> > FQDN is "www.slsware.dmz" is because the first instance of "srv" in
> > the /etc/hosts is:
> > 
> >>> 192.168.2.203 www.slsware.dmz wsd srv

> But that isn't the first; it's the fourth. A grep of the hosts file:

Andy is correct.  The line that Andy cited is the first instance of
the name "srv" as a SEPARATE WORD all unto itself.

> > root@srv:~# egrep srv /etc/hosts
> > 127.0.0.1   srv.slsware.org

Does not contain "srv" as a whole word.

> > 216.17.203.66   srv.slsware.org sso

Does not contain "srv" as a whole word.

> > # 192.168.2.203 srv.slsware.dmz srv

Is a comment.  Ignored.

> > 192.168.2.203   www.slsware.dmz wsd srv

THIS one contains srv as a whole word.  So when you do your "hostname -f"
(which I still contend is a rubbish command which serves no useful
purpose, but it's what you seem to want, so I'll roll with it), it
looks up "srv" in this file as a whole word/field, and finds this line
as the first match.

Therefore hostname -f writes "www.slsware.dmz" to stdout.

> > 192.168.2.203   mail.slsware.dmzmsd srv
> > 192.168.2.203   ntp.slsware.dmz ntp srv
> > 192.168.2.203   ns1.slsware.dmz ns1dns1 srv

This is just nonsense.  You've got the whole word "srv" in the file
multiple times.  But it can't resolve to multiple FQDNs using the
"hostname -f" resolution mechanism, which only returns the first match.
The "srv" on these lines is just noise.

I concur with the previous advice to stop using /etc/hosts for this
configuration, and move everything into DNS.

Here's my entire /etc/hosts file from my Internet-facing VPS (originally
imaged by the VPS provider as squeeze, which I have upgraded to wheezy):

greg@remote:~$ cat /etc/hosts
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

127.0.0.1 localhost.localdomain localhost
# Auto-generated hostname. Please do not remove this comment.
199.231.184.176 remote.wooledge.org  remote
::1 localhost ip6-localhost ip6-loopback


This machine acts as a web server for "wooledge.org" and
"mywiki.wooledge.org" and yet neither of those names appears in
/etc/hosts.  Why should they?  They are only meaningful to the web
server.  They are defined in DNS.



Re: [Aptitude-devel] aptitude ~A question

2016-11-14 Thread steve

Dear Axel,

I just wrote an extensive answer to David *before* reading your reply
and it happens that it answers pretty much to what I discovered, which
is that if a backport package exists but the stable one is installed,
the search with ~A$a~i are counted twice. Seems strange at first thought
but maybe I simply haven't understood all the logic behind that.

Thanks.

Steve



Re: [Aptitude-devel] aptitude ~A question

2016-11-14 Thread steve

Hi David,

Coming back to this problem now that I have a bit more time.

As I have been making a lot of testing, this message is a bit long,
sorry for that.



If you follow my recipe, any packages counted twice (as eg in both
the stable and jessie searches) will show up in the diff with a "-".


I have done this first for a = [trusty,jessie$,jessie-backports,stable]
and then for a = now. No output for jessie$.

Then I have done this:

cat jessie-backports.txt trusty.txt stable.txt | sort | diff -u -now.txt > 
diff.txt

The first lines of diff.txt show

i A augeas-lenses   - ensemble de lentilles nécessaire pour que 
i A autogen-doc - automated text file generator - documentat
i A autopoint   - le programme autopoint de GNU gettext 
-i A autopoint   - le programme autopoint de GNU gettext 
i A autotools-dev   - infrastructure de mise à jour pour les fic
i A avahi-daemon- Démon Avahi pour mDNS/DNS-SD  
i A avidemux-common - Free video editor (Internationalization fi

@@ -39,7 +38,6 @@
i A brasero-cdrkit  - cdrkit extensions for the Brasero burning 
i A bridge-utils- utilitaires destinés à configurer un pont 
i A bundler - Manage Ruby application dependencies  
-i A bundler - Manage Ruby application dependencies  
i A bzip2   - Compresseur de fichier par tri de blocs de

i A bzip2-doc   - Compresseur de fichiers de haute qualité -
i A cabextract  - outil d'extraction de fichiers « Microsoft
@@ -51,7 +49,6 @@
i A chromium-inspector  - web browser - page inspection support 
i A cli-common  - fichiers communs à tous les paquets CLI   
i A cmake-data  - fichiers de données pour CMake (modules, m

-i A cmake-data  - fichiers de données pour CMake (modules, 
m
i A colord-data - system service to manage device colour pro
i A colord  - service système pour gérer les profils cou
i A consolekit  - cadre applicatif pour définir et surveille
@@ -75,7 +72,6 @@
i A cups-server-common  - Common UNIX Printing System(tm) - server c
i A cups- système commun d'impression sous Unix - ge
i A dbconfig-common - framework that helps packages to manage da
-i A dbconfig-common - framework that helps packages to manage 
da

…

+i A epdfview- Lightweight pdf viewer based on poppler 
li

Now, for example, we see that autopoint is present twice (once with a
"-" and once with a blank space at the beginning of the line). So if I
understand correctly, the package "autopoint" appears once in both the
concatenation and in the total file and another time only in the
concatenation. Can I see this behaviour using apt-cache?

apt-cache policy autopoint 
autopoint:

 Installé : 0.19.3-2
 Candidat : 0.19.3-2
Table de version :
0.19.8.1-1~bpo8+1 0
   100 http://ftp.ch.debian.org/debian/ jessie-backports/main amd64 Packages
*** 0.19.3-2 0
   500 http://ftp.ch.debian.org/debian/ jessie/main amd64 Packages
   100 /var/lib/dpkg/status


So it seems that it's the jessie version which is installed. But

aptitude search ~Astable~i | grep autopoint
i A autopoint

aptitude search ~Ajessie$~i | grep autopoint
(no output)

aptitude search ~Ajessie-backports~i | grep autopoint
i A autopoint


which contradicts apt-cache! Is this a bug? Same behaviour for the
package cmake-data.


(BTW, this package is taken from jessie but there is an existing
backport package. Is is possible to upgrade to jessie-backports all
jessie packages which have a jessie-backports version?)

The packages with a starting "+" are the obsolete ones.



What information would be thrown away?


The items that were counted.

apples
oranges
grapes
apples
peaches
pineapple
wc -l → 6
number of items to shop for: 5


Ok thanks :-)

Best,
Steve




Re: How to run a script before shutdown?

2016-11-14 Thread rhkramer
On Sunday, November 13, 2016 08:29:46 PM David Christensen wrote:
> On 11/13/2016 11:34 AM, Robert Latest wrote:
> > I want to automatically start a data backup script (to USB or network
> > drive) at each shutdown of my computer.
> 
> Rather than having the system call my backup/ archive scripts, I have my
> backup/ archive scripts call 'shutdown' when they're done.

I'm not the OP, but, wonderful idea!  And, of course, I can pass a parameter 
to my backup script--one case to shutdown after the backup, and one not to 
shutdown!



Re: iptables question

2016-11-14 Thread Henning Follmann
On Mon, Nov 14, 2016 at 12:45:20AM +0100, deloptes wrote:
> Henning wrote:
> 
> > And usually there is no reason for two separate rfc1918 address ranges.
> > Pick one matching your address space needs and design subnets.
> > There is only one single reason for nat: you have more hosts than routable
> > ip addresses. I guess 10.0.0.0 meets even the biggest organizations.
> 
> Thank you for the line of argumentation. As usual if something works for 10y
> it undergoes a lot of changes. So the reason for not using 10.0.0.0
> internally is that it is historically that way. Some years ago the firewall
> was connected to the public network directly. The new provider gave me the
> modem and it uses automatically 10.0.0.0, which I can not influence. I just
> did the DMZ - this was the time I tried to rewrite the firewall rules, but
> I found out I need to read again a lot about iptables and more important it
> would mean I would need to experiment and jeopardize the network.
> The setup is useful in the way that the whole wireless network is outside
> the firewall in the 10.0.0.0/24 range. All that I need for operating works
> perfectly. Now the only problem is that I can not access anything else on
> the 10.0.0.0 network except the modem.
> 
> thanks again
> 
> 

Last time I chime in here.
I understand growth and chaos, believe me. However sometimes we need a
nudge or a kick in the but to clean up. Maybe this is your call.
Simplicity is a beautiful thing my friend.


-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com



Re: (deb-cat) Zoho per les llistes de Debian?

2016-11-14 Thread Narcis Garcia
D'acord, em sembla que és el remitent original el què havia utilitzat
Zoho, i no par el Listmaster/Bounces de Debian.



__
I'm using this express-made address because personal addresses aren't
masked enough at lists.debian.org archives.
El 14/11/16 a les 12:40, Narcis Garcia ha escrit:
> Acabo de rebre un avís per aquesta incidència:
> https://lists.debian.org/bounces/2durpe845PK9k7r173rLdg
> 
> A la qual veig les línies que han causat que no se superés el filtre
> anti-brossa: les que fan referència als serveis de l'empresa
> d'assetjament publicitari «Zoho».
> 
> Com és que es fa servir això?
> 



Zoho per les llistes de Debian?

2016-11-14 Thread Narcis Garcia
Acabo de rebre un avís per aquesta incidència:
https://lists.debian.org/bounces/2durpe845PK9k7r173rLdg

A la qual veig les línies que han causat que no se superés el filtre
anti-brossa: les que fan referència als serveis de l'empresa
d'assetjament publicitari «Zoho».

Com és que es fa servir això?
-- 


__
I'm using this express-made address because personal addresses aren't
masked enough at lists.debian.org archives.



Re: How to run a script before shutdown?

2016-11-14 Thread Hans
Maybe you might want to take a look at the package "backintime-kde"?
It may fit all your needs.

Good luck!

Hans



Re: How to run a script before shutdown?

2016-11-14 Thread Michael Lange
Hi,

On Sun, 13 Nov 2016 20:34:38 +0100
Robert Latest  wrote:

> Hi all,
> 
> I want to automatically start a data backup script (to USB or network
> drive) at each shutdown of my computer. I did some research into this
> and found that several people have the same problem as I do. But the
> threads I found petered out into discussions of several ways of doing
> this, working for some people and not for others.  So here I am
> wondering if there is a canonical, proper and reliable method of doing
> this.

probably not the "canonical" way, but still works:
I have a script in /etc/init.d/mystuff for a similar task, that looks
basically like

case "$1" in
start)
printf "/usr/sbin/ntpdate-debian -s -b -p 8 -u de.pool.ntp.org" | at 
now + 2 minutes
;;
stop)
RUNL=`/sbin/runlevel`
case ${RUNL:2:3} in 0)
/usr/local/sbin/sys-backup;;
esac
;;
esac

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Humans do claim a great deal for that particular emotion (love).
-- Spock, "The Lights of Zetar", stardate 5725.6



Re: iptables question

2016-11-14 Thread deloptes
deloptes wrote:

> Igor Cicimov wrote:
> 
>> Run tcpdump and check whats happening
> 
> That is strange - I will look into this direction - let me know if you
> have any ideas
> 
> regards
> 
> 
> tcpdump -vvv dst 10.0.0.7
> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size
> 65535 bytes
> 08:07:11.591763 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has RM696
> tell 10.0.0.1, length 28
> 08:07:12.591729 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has RM696
> tell 10.0.0.1, length 28
> 08:07:13.591686 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has RM696
> tell 10.0.0.1, length 28
> 08:07:14.595695 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has RM696
> tell 10.0.0.1, length 28
> 08:07:15.595632 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has RM696
> tell 10.0.0.1, length 28
> 08:07:16.595620 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has RM696
> tell 10.0.0.1, length 28
> 
> 
> 
> tcpdump -vvv dst 10.0.0.138
> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size
> 65535 bytes
> 08:04:55.765744 IP (tos 0x0, ttl 63, id 26002, offset 0, flags [DF], proto
> TCP (6), length 60)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [S], cksum 0xc2c6 (correct),
> seq
> 2408995280, win 29200, options [mss 1460,sackOK,TS val 223296578 ecr
> 0,nop,wscale 7], length 0
> 08:04:55.767594 IP (tos 0x0, ttl 63, id 26003, offset 0, flags [DF], proto
> TCP (6), length 40)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [.], cksum 0x242c (correct),
> seq
> 2408995281, ack 3147433360, win 229, length 0
> 08:04:55.772423 IP (tos 0x0, ttl 63, id 44890, offset 0, flags [none],
> proto UDP (17), length 69)
> 10.0.0.1.24455 > 10.0.0.138.domain: [udp sum ok] 7454+ PTR?
> 138.0.0.10.in-addr.arpa. (41)
> 08:04:55.774778 IP (tos 0x0, ttl 63, id 26004, offset 0, flags [DF], proto
> TCP (6), length 79)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [P.], cksum 0xfb15 (correct),
> seq
> 0:39, ack 1, win 229, length 39
> 08:04:55.787360 IP (tos 0x0, ttl 63, id 26005, offset 0, flags [DF], proto
> TCP (6), length 40)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [.], cksum 0x23eb (correct),
> seq
> 39, ack 27, win 229, length 0
> 08:04:55.789504 IP (tos 0x0, ttl 63, id 26006, offset 0, flags [DF], proto
> TCP (6), length 1500)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [.], cksum 0x7c86 (correct),
> seq
> 39:1499, ack 27, win 229, length 1460
> 08:04:55.789680 IP (tos 0x0, ttl 63, id 26007, offset 0, flags [DF], proto
> TCP (6), length 228)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [P.], cksum 0x46dd (correct),
> seq
> 1499:1687, ack 27, win 229, length 188
> 08:04:55.791326 IP (tos 0x0, ttl 63, id 26008, offset 0, flags [DF], proto
> TCP (6), length 312)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [P.], cksum 0xb0d6 (correct),
> seq
> 1687:1959, ack 339, win 237, length 272
> 08:04:55.796226 IP (tos 0x0, ttl 63, id 44893, offset 0, flags [none],
> proto UDP (17), length 67)
> 10.0.0.1.63625 > 10.0.0.138.domain: [udp sum ok] 17121+ PTR?
> 1.0.0.10.in-addr.arpa. (39)
> 08:04:58.223139 IP (tos 0x0, ttl 63, id 26009, offset 0, flags [DF], proto
> TCP (6), length 56)
> 10.0.0.1.52112 > 10.0.0.138.ssh: Flags [P.], cksum 0x0ea9 (correct),
> seq
> 1959:1975, ack 915, win 246, length 16



My wife turned off the wireless

08:59:06.127029 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has RM696
tell 10.0.0.1, length 28
08:59:06.202411 IP (tos 0x0, ttl 63, id 50126, offset 0, flags [DF], proto
TCP (6), length 60)
10.0.0.1.34912 > RM696.ssh: Flags [S], cksum 0x5a12 (correct), seq
3855619686, win 29200, options [mss 1460,sackOK,TS val 226547112 ecr
0,nop,wscale 7], length 0
08:59:07.172012 IP (tos 0x0, ttl 63, id 50127, offset 0, flags [DF], proto
TCP (6), length 60)
10.0.0.1.34912 > RM696.ssh: Flags [S], cksum 0x55fa (correct), seq
3855619686, win 29200, options [mss 1460,sackOK,TS val 226548160 ecr
0,nop,wscale 7], length 0
08:59:09.219907 IP (tos 0x0, ttl 63, id 50128, offset 0, flags [DF], proto
TCP (6), length 60)
10.0.0.1.34912 > RM696.ssh: Flags [S], cksum 0x4dfa (correct), seq
3855619686, win 29200, options [mss 1460,sackOK,TS val 226550208 ecr
0,nop,wscale 7], length 0
08:59:13.251697 IP (tos 0x0, ttl 63, id 50129, offset 0, flags [DF], proto
TCP (6), length 60)
10.0.0.1.34912 > RM696.ssh: Flags [S], cksum 0x3e3a (correct), seq
3855619686, win 29200, options [mss 1460,sackOK,TS val 226554240 ecr
0,nop,wscale 7], length 0
08:59:21.571248 IP (tos 0x0, ttl 63, id 50130, offset 0, flags [DF], proto
TCP (6), length 60)
10.0.0.1.34912 > RM696.ssh: Flags [S], cksum 0x1dba (correct), seq
3855619686, win 29200, options [mss 1460,sackOK,TS val 226562560 ecr
0,nop,wscale 7], length 0
08:59:37.954393 IP (tos 0x0, ttl 63, id 50131, offset 0, flags [DF], proto
TCP (6), length 60)
10.0.0.1.34912 > RM696.ssh: Flags [S], cksum 0xddb9 (correct), seq
3855619686, win 29200, options [mss 1460,sackOK,TS val 226578944 ecr
0,nop,wscale 7],