Displaying 20 results from an estimated 2000 matches similar to: "globbing doesn't work locally"
2003 Aug 16
1
globbing doesn't work locally
This is on rsync v2.4.5 on RedHat 7.3.
If I do something like
rsync ... 'somehost:/path/to/files.*' /local/path
it works fine, but if I do
rsync ... '/local/path/to/files.*' somehost:/path/to
globbing fails, yielding an error about being unable to find a file
named 'files.*':
link_stat /local/path/to/files.* : No such file or directory
rsync error: partial
2013 Dec 09
2
[PATCH] sysprep: allow to specify globbing for --delete
Adapt the globbing part from the old --remote-path work previously
proposed for sysprep [1], allowing --delete to perform globbing when
deleting paths.
[1] https://www.redhat.com/archives/libguestfs/2013-October/msg00045.html
---
sysprep/sysprep_operation_delete.ml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/sysprep/sysprep_operation_delete.ml
2009 Jul 11
2
[PATCH] include parameters can handle globbing
Hey guys,
This patch will allow you to include different configuration files in
the main dovecot.conf by using globbing [1] (like Apache for instance).
!include = conf.d/*.conf
!include_try = /etc/dovecot/extra*
So with this you can split the dovecot.conf in different smaller
configuration files. It's more the debian way to do that. But it's very
handy if you have to generate
2007 Jul 02
6
Testing route globbing and limitations of get()
Hi everyone,
I''m new to rails and also to rspec, but I tried to do my homework. To answer
my questions, I searched this list''s archives, the Rails API, and Google, to
no avail. Therefor, I''d be grateful if someone could point me in the right
directions:
1) There doesn''t seem to be a counterpart to assert_recognizes in rspec.
route_for() won''t work
2008 Apr 11
2
DO NOT REPLY [Bug 5388] New: wildcards and rsync 3.01+
https://bugzilla.samba.org/show_bug.cgi?id=5388
Summary: wildcards and rsync 3.01+
Product: rsync
Version: 3.0.2
Platform: x86
OS/Version: FreeBSD
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: support@reverse.net
QAContact:
2009 Apr 07
4
DO NOT REPLY [Bug 6251] New: security: rsync executes remote commands
https://bugzilla.samba.org/show_bug.cgi?id=6251
Summary: security: rsync executes remote commands
Product: rsync
Version: 3.0.5
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: mueller@relog.ch
2010 Oct 04
1
Globbing inconsistencies, dir() vs. unlink()
I was trying to remove a directory and couldn't figure out why it was
failing:
> dir("~/p4/r-packages/IREval/Users", recursive=T)
[1] "u0048513/p4/r-packages/IREval/DESCRIPTION"
[2] "u0048513/p4/r-packages/IREval/R/IREval.R"
[3] "u0048513/p4/r-packages/IREval/Read-and-delete-me"
[4] "u0048513/p4/r-packages/IREval/tests/general.R"
>
2000 Jul 15
0
openssh-2.1.1p3 - problem with -i option
Greetings:
I've just attempted to upgrade from openssh-2.1.1p1 to openssh-2.1.1p3
and I'm having problems with the server component. My system runs RedHat
Linux 6.2 (x86 version) with all currently released updates applied.
The sshd daemon is being spawned by xinetd with the -i option and worked
fine with the p1 level release.
Now, when a remote client attempts to connect to the daemon,
2020 May 17
2
[Bug 3165] New: man sshd_config does not define order of includes when using globbing
https://bugzilla.mindrot.org/show_bug.cgi?id=3165
Bug ID: 3165
Summary: man sshd_config does not define order of includes when
using globbing
Product: Portable OpenSSH
Version: 8.2p1
Hardware: amd64
OS: Linux
Status: NEW
Severity: trivial
Priority: P5
Component: sshd
2005 Jan 14
1
--delete & --files-from can't be used as a purge list. Alternate strategy suggestions?
Hi,
N.B. rsync version 2.6.2 on Linux, no rsync server, using SSH
THE PROBLEM
rsync --delete
--files-from=<FILES_ON_MASTER_TO_BE_DEL_AND_NOT_ON_SECONDARY> -e ssh
-... <SECONDARY_HOST>:<BASEDIR> <BASEDIR>
generates error:
receiving file list ... link_stat "<EXAMPLE_FILE_NOT_ON_SECONDARY"
failed: No such file or directory
and does not have the desired
2013 Dec 09
0
Re: [PATCH] sysprep: allow to specify globbing for --delete
On Mon, Dec 09, 2013 at 04:19:12PM +0100, Pino Toscano wrote:
> Adapt the globbing part from the old --remote-path work previously
> proposed for sysprep [1], allowing --delete to perform globbing when
> deleting paths.
>
> [1] https://www.redhat.com/archives/libguestfs/2013-October/msg00045.html
> ---
> sysprep/sysprep_operation_delete.ml | 4 +++-
> 1 file changed, 3
2016 Feb 03
0
[PATCH 3/3] customize: add globbing for --delete
Support globbing in paths passed to --delete, telling glob to not
return directories with leading slash.
This re-adds back globbing for --delete in virt-sysprep, which was
available before the integration with common code from virt-customize.
---
customize/customize_run.ml | 2 +-
generator/customize.ml | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git
2016 Feb 04
0
[PATCH v2 2/2] customize: add globbing for --delete
Support globbing in paths passed to --delete, telling glob to not
return directories with leading slash.
This re-adds back globbing for --delete in virt-sysprep, which was
available before the integration with common code from virt-customize.
---
customize/customize_run.ml | 2 +-
generator/customize.ml | 6 ++++++
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git
2014 Feb 13
1
[Bug 10445] New: flag to suppress link_stat error messages
https://bugzilla.samba.org/show_bug.cgi?id=10445
Summary: flag to suppress link_stat error messages
Product: rsync
Version: 3.1.1
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: mij at bitchx.it
2011 Mar 02
1
Bug#616103: logcheck: (re)enable globbing of logfile names
Package: logcheck
Version: 1.3.13
Severity: minor
Tags: patch
In Lenny it was possible to use wildcards in logcheck.logfiles. For
example, I used: /var/log/HOSTS/*/*.log
root at durer:~# su -s /bin/bash -c "bash -x /usr/sbin/logcheck" logcheck
<cut>
+ read file
+ logoutput '/var/log/HOSTS/*/*.log'
+ file='/var/log/HOSTS/*/*.log'
+ debug 'logoutput called
2019 Oct 04
1
imapsieve administrator scripts are not executed in the order they are defined
Dear dovecot developers,
I have an issue with the Pigeonhole IMAPSieve Plugin and the order in which
administrator scripts are executed. Although I cannot find anything about the
order in which the scripts are executed, I would expect they are executed in
the order they are defined: the one defined by imapsieve_mailbox1_* before the
one defined by imapsieve_mailbox2_* in case both match.
I
2006 Jun 12
1
nmblookup receives response, but doesn't show it
Hi folks,
I find that nmblookup seems to be receiving
responses to name queries, but ignoring them. Here's what's
happening:
# nmblookup somehost
querying somehost on x.y.255.255
name_query failed to find name somehost
But watching the transaction with ethereal on the local
host, I see that:
1. nmblookup on local udp port nnnn (some random number above 1024)
sends an nbns
2006 Jun 29
0
Asterisk with Sipbroker calling / routing problem
Hello all,
I've been using * for quite some time and yesterday I decided to add
sipbroker to my config. It was pretty simple and it works for some
numbers (e.g. I can call *258-9123, UK date & time - which is on the
"phone numbers you can call" page -) but fails for some others.
For example I've got a friend who's at freephonie so to call him, I
would dial
2013 Oct 01
2
sshd accepted fingerprint logging
Currently, LogLevel must be set to VERBOSE to see the fingerprint of an
accepted key, and the default LogLevel is INFO. Since this is useful
security information, I would like to propose that the 'Accepted
publickey' message be modified to include the fingerprint of the
accepted key. Is this a reasonable solution?
Here is an example log snippet with LogLevel VERBOSE:
Oct 1 15:23:24
2005 Mar 31
1
X11 forwarding and session multiplexing
Hi,
A user has noticed that X11 forwarding does not appear to work when using session
multiplexing. It seems that the DISPLAY environment variable is not getting
set in the slave sessions.
Any thought? The ~/.ssh/config ib below.
Host somehost-master
ControlMaster yes
ControlPath ~/.ssh/somehost.sock
HostbasedAuthentication no
HostName somehost
Host somehost-slave
ControlPath