Question to rsync

[Hans]

Hi folks,

I am looking for an option in rsync, which I can not find any more. I read the 
manual, but in the manual I could nor find the optiuon I am looking for. 

In earlier versions, there was rsync -av -d, where "-d" was the tag, which 
did, what I wanted: I want to delete any files in the target,. when they are 
not existing in the source.

I am sure, this option stilll exists in the  actual rsync version, but I  can 
not find it (although, there is a "--delete", but looks to do something else)

Does anyone know, where the required function is hidden?

Thanks for any hints.

Best regards

Hans

Re: Question to rsync

[Alberto Luaces]

Hans writes:

> I am sure, this option stilll exists in the  actual rsync version, but I  can 
> not find it (although, there is a "--delete", but looks to do something else)

I have always used "--delete" for that purpose.  I interpret the
"extraneous" term in the manpage as "not found in the target".

-- 
Alberto

Re: Question to rsync

[Teemu Likonen]

Hans [2018-06-22 11:04:43+02] wrote:

> In earlier versions, there was rsync -av -d, where "-d" was the tag,
> which did, what I wanted: I want to delete any files in the target,.
> when they are not existing in the source.
>
> I am sure, this option stilll exists in the actual rsync version, but
> I can not find it (although, there is a "--delete", but looks to do
> something else)

In the rsync(1) man page there are long descriptions of --delete and
different --delete-* options. I'm sure you will find the one that suits
your needs (probably --delete).

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: Question to rsync

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 22, 2018 at 11:04:43AM +0200, Hans wrote:
> Hi folks,
> 
> I am looking for an option in rsync, which I can not find any more. I read 
> the 
> manual, but in the manual I could nor find the optiuon I am looking for. 
> 
> In earlier versions, there was rsync -av -d, where "-d" was the tag, which 
> did, what I wanted: I want to delete any files in the target,. when they are 
> not existing in the source.

As others have said, this is --delete. Options -d and -D are taken for other
things -- and I don't remember that "-d" has meant delete for quite a long
time (say 10 years or so).

> I am sure, this option stilll exists in the  actual rsync version, but I  can 
> not find it (although, there is a "--delete", but looks to do something else)

No, this is what you are looking for. As Teemu pointed out, the --delete-*
options are worth a look. For example, if you have big files (videos) which
you rename often at the source, you better use option -y. Then rsync tries
to use a suitable file at the target as basis instead of pushing the whole
thing through the wire. Now, if *that* file has been deleted before... bad
luck. So combining -y --delete-after (or better --delete-delay) can speed
up things significantly. Unless... you are memory constrained or your wire
is very fast.

Decisions, decisions...

;-)

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

iEYEARECAAYFAlsswrMACgkQBcgs9XrR2kbd+wCdGfHA8A20cvVDw8uhB9ariro2
cQUAn3pbs7cA/2Cg2h+i5zHzL6kSSl/3
=SQjr
-END PGP SIGNATURE-

[SOLVED] Re: Question to rsync

[Hans]

Am Freitag, 22. Juni 2018, 11:34:43 CEST schrieb to...@tuxteam.de:
Thank you Tomas, and all the others for the fast response. 

I believe, the --delete option will doi the trick for me. 

I want to sync two mail folders, so that I see my mails in Plasma and also in 
Trinity, so that I regularlöy sync tzhe plasma-(kmail)-folder to trinitý-
(kmail)-folder with a cronjob. 

Sop, whern I delete a mail in plasma, it shall also be deleted in the next 
sync in trinity. So I am sure, as you described, the --delete option will do 
this.

Thanks for the fast solution.

Have a nice weekend

Hans 
> As others have said, this is --delete. Options -d and -D are taken for other
> things -- and I don't remember that "-d" has meant delete for quite a long
> time (say 10 years or so).
> 
> > I am sure, this option stilll exists in the  actual rsync version, but I 
> > can not find it (although, there is a "--delete", but looks to do
> > something else)
> No, this is what you are looking for. As Teemu pointed out, the --delete-*
> options are worth a look. For example, if you have big files (videos) which
> you rename often at the source, you better use option -y. Then rsync tries
> to use a suitable file at the target as basis instead of pushing the whole
> thing through the wire. Now, if *that* file has been deleted before... bad
> luck. So combining -y --delete-after (or better --delete-delay) can speed
> up things significantly. Unless... you are memory constrained or your wire
> is very fast.
> 
> Decisions, decisions...
> 
> ;-)
> 
> Cheers
> -- t

Re: [SOLVED] Re: Question to rsync

[john doe]

On 6/22/2018 11:47 AM, Hans wrote:

Am Freitag, 22. Juni 2018, 11:34:43 CEST schrieb to...@tuxteam.de:
Thank you Tomas, and all the others for the fast response.

I believe, the --delete option will doi the trick for me.

I want to sync two mail folders, so that I see my mails in Plasma and also in
Trinity, so that I regularlöy sync tzhe plasma-(kmail)-folder to trinitý-
(kmail)-folder with a cronjob.

Sop, whern I delete a mail in plasma, it shall also be deleted in the next
sync in trinity. So I am sure, as you described, the --delete option will do
this.



From:

https://linux.die.net/man/1/rsync

"I mirror a directory between my lqoldrq and lqnewrq ftp sites with the 
command:

CWrsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge"
This is launched from cron every few hours."

--
John Doe

Re: [SOLVED] Re: Question to rsync

[rhkramer]

On Friday, June 22, 2018 05:58:52 AM john doe wrote:
> From:
> 
> https://linux.die.net/man/1/rsync
> 
> "I mirror a directory between my lqoldrq and lqnewrq ftp sites with the
> command:
> CWrsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge"
> This is launched from cron every few hours."

For education, I started skimming the man page trying to find out what the "CW" 
is -- I haven't found anything so far.

???

Re: [SOLVED] Re: Question to rsync

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 22, 2018 at 06:39:11AM -0400, rhkra...@gmail.com wrote:
> On Friday, June 22, 2018 05:58:52 AM john doe wrote:
> > From:
> > 
> > https://linux.die.net/man/1/rsync
> > 
> > "I mirror a directory between my lqoldrq and lqnewrq ftp sites with the
> > command:
> > CWrsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge"
> > This is launched from cron every few hours."
> 
> For education, I started skimming the man page trying to find out what the 
> "CW" 
> is -- I haven't found anything so far.

I think this is spurious -- perhaps the inner thoughts of the
poster's editor escaping the consciousness barrier. As you might
find ":wq" beneath some of my mails, because I'm using vim to
compose them...

Whatever it is, it's part of the command, so you probably won't
find it in rsync's man page but rather in some CWrsync's man page,
if it exists at all.

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

iEYEARECAAYFAlss1PoACgkQBcgs9XrR2kZhOQCfZ2kgJGByGdHhlz/OAc26LRJR
F/4AnAp6FnOp1JQ9gWzK2HunDsaQk68j
=66OH
-END PGP SIGNATURE-

Re: [SOLVED] Re: Question to rsync

[john doe]

On 6/22/2018 12:39 PM, rhkra...@gmail.com wrote:

On Friday, June 22, 2018 05:58:52 AM john doe wrote:

From:

https://linux.die.net/man/1/rsync

"I mirror a directory between my lqoldrq and lqnewrq ftp sites with the
command:
CWrsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge"
This is launched from cron every few hours."


For education, I started skimming the man page trying to find out what the "CW"
is -- I haven't found anything so far.

???



From:

https://en.wikipedia.org/wiki/CwRsync

"cwRsync is an implementation of Rsync for Windows."

--
John Doe

Re: [SOLVED] Re: Question to rsync

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 22, 2018 at 12:56:44PM +0200, john doe wrote:

[...]

> "cwRsync is an implementation of Rsync for Windows."

Ah, that's a better explanation, thanks :)

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

iEYEARECAAYFAlss13AACgkQBcgs9XrR2kazJQCePdWTuZ+sTL8YIfVJieiPGucE
nroAn1N0cq3Xn6UNhFKp8k4y401vAmNO
=Un7a
-END PGP SIGNATURE-

Re: [SOLVED] Re: Question to rsync

[Stefan Krusche]

Am Freitag 22 Juni 2018 schrieb Hans:
> Am Freitag, 22. Juni 2018, 11:34:43 CEST schrieb to...@tuxteam.de:
> Thank you Tomas, and all the others for the fast response. 
> 
> I believe, the --delete option will doi the trick for me. 
> 
> I want to sync two mail folders, so that I see my mails in Plasma and also in 
> Trinity, so that I regularlöy sync tzhe plasma-(kmail)-folder to trinitý-
> (kmail)-folder with a cronjob. 
> 
> Sop, whern I delete a mail in plasma, it shall also be deleted in the next 
> sync in trinity. So I am sure, as you described, the --delete option will do 
> this.
> 
> Thanks for the fast solution.
> 
> Have a nice weekend
> 

Hallo Hans,

I've always successfully synced the kmail (Trinity) data directory between 
system with this command:
rsync -avuh --delete $HOME/.trinity/share/apps/kmail/ 
user@otherhost:.trinity/share/apps/kmail

You can, as you probably know, test with "-n", which only outputs, what rsync 
would do, and in case it's too much output, pipe that through less.

But, I have also synced kmail's config files:
rsync -avuh --delete $HOME/.trinity/share/config/{kmail,email}* 
user@otherhost:.trinity/share/config/

Regards,
Stefan

Re: [SOLVED] Re: Question to rsync

[Gene Heskett]

On Friday 22 June 2018 06:39:11 rhkra...@gmail.com wrote:

> On Friday, June 22, 2018 05:58:52 AM john doe wrote:
> > From:
> >
> > https://linux.die.net/man/1/rsync
> >
> > "I mirror a directory between my lqoldrq and lqnewrq ftp sites with
> > the command:
> > CWrsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge"
> > This is launched from cron every few hours."
>
> For education, I started skimming the man page trying to find out what
> the "CW" is -- I haven't found anything so far.
>
> ???
Obviously a copy/paste error, throw it away.


-- 
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: Ntp not working

[Mike]

On Thu, Jun 21, 2018 at 10:04:24AM +0300, David Baron wrote:
> On Wed, Jun 20, 2018, 5:33 PM Mike  wrote:
> 
> >
> > OK, so your NTP servers are:
> >
> > pool 0.debian.pool.ntp.org iburst
> > pool 1.debian.pool.ntp.org iburst
> > pool 2.debian.pool.ntp.org iburst
> > pool 3.debian.pool.ntp.org iburst
> >
> >
> > Most likely you are blocking UDP/123.  However, if you fail to resolve
> > the IP when you ping it, you have a DNS issue.
> >
> > Mike.
> >
> 
> 123 udp allowed both ways.
> The destination is resolved do dns ok.
> Ping still fails, unreachable,sendmsg operation not permitted.
>

The npt config is correct and the servers should be reachable.  This
points to some kind of networking issue at your end.

That ping error is a little curious.  It does sounds like a permissions
issue.  One needs to be root to send the ICMP messages that ping uses.
Ping gets around this issue by having setuid set on /usr/bin/ping, so
that anyone who can run it runs it effectively as root.  I've never
tried it but I suspect that if you remove setuid from /usr/bin/ping
you'd probably see the above error.  Having said that, I did a quick
seearch with a well-known Internet search engine and it the results
suggested that iptables could also cause the above error.

Anyway, speculation aside, the error (and I've ran ping many, many times
and never seen that error before) does suggest that something isn't
right on your box and it's not the NTPd config.  I'd start by looking at
your iptables config.  I'd be fairly sure something is blocking UDP/123,
whereever it is.

Mike. 


signature.asc
Description: PGP signature

Re: [SOLVED] Re: Question to rsync

[Teemu Likonen]

rhkra...@gmail.com [2018-06-22 06:39:11-04] wrote:

> On Friday, June 22, 2018 05:58:52 AM john doe wrote:
>> "I mirror a directory between my lqoldrq and lqnewrq ftp sites with the
>> command:
>> CWrsync -az -e ssh --delete ~ftp/pub/samba nimbus:"~ftp/pub/tridge"
>> This is launched from cron every few hours."
>
> For education, I started skimming the man page trying to find out what
> the "CW" is -- I haven't found anything so far.

I think it originates from the man page code, Roff typesetting language.
Here's my copy of the part section in /usr/share/man/man1/rsync.1.gz:


.PP 
I mirror a directory between my \(dq\&old\(dq\& and \(dq\&new\(dq\& ftp sites 
with the
command:
.PP 
\f(CWrsync \-az \-e ssh \-\-delete ~ftp/pub/samba 
nimbus:\(dq\&~ftp/pub/tridge\(dq\&\fP
.PP 
This is launched from cron every few hours.

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Booting once on a different OS (with grub)

[Pétùr]

Is there a way to tell grub to boot the next time (and only this time)
to a different OS than the default one?

I have a bluetooth keyboard which does not work in grub. This is why
I want to tell grub, while I am on debian, to boot at the next reboot
to entry n°3 (which is a window I keep for some specific softwares).

I do not want to change grub order each time. I am looking more to
something like "touch /forcefsck" to force check filesystem (but for
booting to entry 3 in grub).

Pétùr

Re: [SOLVED] Re: Question to rsync

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 22, 2018 at 03:50:43PM +0300, Teemu Likonen wrote:

[...]

> \f(CWrsync \-az \-e ssh \-\-delete ~ftp/pub/samba 
> nimbus:\(dq\&~ftp/pub/tridge\(dq\&\fP

YES! That's it! (uh -- sorry for shouting :)

This one makes most sense. And it is case-correct, too.

Thanks for solving that conundrum :-D

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

iEYEARECAAYFAlss8ngACgkQBcgs9XrR2kb0GQCfbMqSvyVLel3GpfQdBnqzUSsS
ccIAniLVwS7jsXm4W+QV1abSUtctDxk8
=8+Sm
-END PGP SIGNATURE-

Re: Booting once on a different OS (with grub)

[davidson]

On Fri, 22 Jun 2018, Pétùr wrote:


Is there a way to tell grub to boot the next time (and only this time)
to a different OS than the default one?


   $ man -k reboot
   grub-reboot (8) - set the default boot entry for GRUB, for the next
   boot only
   [snip]

Caveat: I have never used it.

   $ man grub-reboot

   GRUB-REBOOT(8)  System Administration UtilitiesGRUB-REBOOT(8)

   NAME
  grub-reboot - set the default boot entry for GRUB, for the
  next boot only

   SYNOPSIS
  grub-reboot [OPTION] MENU_ENTRY

   DESCRIPTION
  Set the default boot menu entry for GRUB, for the next boot only.

  -h, --help
 print this message and exit

  -V, --version
 print the version information and exit

  --boot-directory=DIR
 expect GRUB images under the directory DIR/grub
 instead of the /boot/grub directory

  MENU_ENTRY is a number, a menu item title or a menu item
  identifier.

  Please note that menu items in submenus or sub-submenus
  require specifying the submenu components and then the menu
  item component.  The titles should be separated using the
  greater-than character (>) with no extra spaces.

  Depending on your shell some characters including > may need
  escaping. More information about this is available in the
  GRUB Manual in the section about the 'default' command.


I have a bluetooth keyboard which does not work in grub. This is why
I want to tell grub, while I am on debian, to boot at the next reboot
to entry n°3 (which is a window I keep for some specific softwares).

I do not want to change grub order each time. I am looking more to
something like "touch /forcefsck" to force check filesystem (but for
booting to entry 3 in grub).


Good luck.

ldap and rfc2307bis

[malcolm moore]

How do I get rid of nis.schema and add rfc2307bis on slapd 
I'm using Buster ( 22June )

This has been driving me nuts now all day ... any help please
Ta
M
 

Re: [SOLVED] Re: Question to rsync

[rhkramer]

Thanks!

On Friday, June 22, 2018 06:56:44 AM john doe wrote:
> From:
> 
> https://en.wikipedia.org/wiki/CwRsync
> 
> "cwRsync is an implementation of Rsync for Windows."

Re: Expired GPG keys of older release

[James Cloos]

> "T" ==  writes:

T> And just extending the keys' validity (as someone proposed in this
T> thread) seems a bad idea too, since the requirement for secure keys
T> evolves over time, as the NSA^H^H^H bad guys buy more GPUs.

The problem is that the point of a key's expiration time is that
signatures newer than that should fail, but all signatures made before
the expiration should verify.

So, if apt's signature verification only looks at the key's expiration
date and not at the signature's timestamp, that is a bug.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Re: Expired GPG keys of older release

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 22, 2018 at 02:39:52PM -0400, James Cloos wrote:
> > "T" ==  writes:
> 
> T> And just extending the keys' validity (as someone proposed in this
> T> thread) seems a bad idea too, since the requirement for secure keys
> T> evolves over time, as the NSA^H^H^H bad guys buy more GPUs.
> 
> The problem is that the point of a key's expiration time is that
> signatures newer than that should fail, but all signatures made before
> the expiration should verify.

Makes sense...

> So, if apt's signature verification only looks at the key's expiration
> date and not at the signature's timestamp, that is a bug.

Hm. But a stern warning (along the lines "this signature isn't as secure
as it used to be") seems in order, no?

For the current case, what's needed most is some kind of workaround, since
an old apt can't be fixed retroactively, though.

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

iEYEARECAAYFAlstSjMACgkQBcgs9XrR2kbbawCePl226Au0nqDGjo7qEUD62cTV
QzIAnRbBCpIyFXPsR4JC9H7VtI99moyA
=UFsZ
-END PGP SIGNATURE-

Re: Expired GPG keys of older release

[David Wright]

On Fri 22 Jun 2018 at 21:12:51 (+0200), to...@tuxteam.de wrote:
> On Fri, Jun 22, 2018 at 02:39:52PM -0400, James Cloos wrote:
> > > "T" ==  writes:
> > 
> > T> And just extending the keys' validity (as someone proposed in this
> > T> thread) seems a bad idea too, since the requirement for secure keys
> > T> evolves over time, as the NSA^H^H^H bad guys buy more GPUs.
> > 
> > The problem is that the point of a key's expiration time is that
> > signatures newer than that should fail, but all signatures made before
> > the expiration should verify.
> 
> Makes sense...
> 
> > So, if apt's signature verification only looks at the key's expiration
> > date and not at the signature's timestamp, that is a bug.
> 
> Hm. But a stern warning (along the lines "this signature isn't as secure
> as it used to be") seems in order, no?
> 
> For the current case, what's needed most is some kind of workaround, since
> an old apt can't be fixed retroactively, though.

Well, I attempted to supply that in
https://lists.debian.org/debian-user/2018/06/msg00528.html
but I have no idea whether that would be achievable in docker
or not because the suggestion has had no follow-up.

BTW Reading your "Keys *have* to expire at some point, and you can't
re-sign archived packages with a fresh key", it's not clear why the
expired key can't be unexpired, ie given an expiration date in the
future, if it's known to be still good.

Cheers,
David.

Re: Expired GPG keys of older release

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Jun 22, 2018 at 11:48:00PM -0500, David Wright wrote:
> On Fri 22 Jun 2018 at 21:12:51 (+0200), to...@tuxteam.de wrote:

[...]

> Well, I attempted to supply that in
> https://lists.debian.org/debian-user/2018/06/msg00528.html
> but I have no idea whether that would be achievable in docker
> or not because the suggestion has had no follow-up.

I'm not the docker guy, and there are lots of "interesting" things
around, so I won't be the one. But I'm curious too...

> BTW Reading your "Keys *have* to expire at some point, and you can't
> re-sign archived packages with a fresh key", it's not clear why the
> expired key can't be unexpired, ie given an expiration date in the
> future, if it's known to be still good.

Yes, you're right: a GPG key's validity can be extended with a new
certificate (whether it's responsible to do is another thing, since
available computing power grows, *and* there has been more time to
hack at this key, its crypto, and for things to leak). So practically
speaking still keys have to expire at some point.

The only way out would be for an archive declared immutable to set
up an attestation service which signs (state-of-the-art) package
hashes with (state-of-the-art) signing procedures and refreshes
things periodically. Debian hasn't decided to set that up, a thing
I can understand.

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

iEYEARECAAYFAlst76cACgkQBcgs9XrR2kYeLgCaAibgQsc+ZemhfmKjZIalrKWF
pZsAn0Y3ktHGU9QJaKveKZSEUfr0ZIQb
=5MG1
-END PGP SIGNATURE-