I have three servers. nginx00 (master nginx server) and nginx01 and nginx02
(slave nginx servers).
nginx00 is a staging environment that I do testing on. Once it goes live I run
a bash script that syncs the config files and restarts the nginx daemon. It's
working fine as root. However, I am
On Fri, Jun 17, 2016 at 11:21:42AM +0100, Dean Wakerley wrote:
> I ran into this problem when trying to buiild a TCL extension. Building
> the extension requires pulling in with source tclConfig.sh which
> provides various settings. TCL_DEFS contains space separated -D
> arguments to pass
On 6/17/16 6:21 AM, Dean Wakerley wrote:
> Bash Version: 4.3
> Patch Level: 42
> Release Status: release
>
> Description:
> The expansion of a variable containing spaces splits on all spaces
> including escaped/backslashed space.
This analysis isn't correct, and the description above describes
On Fri, 17 Jun 2016 11:21:42 +0100, Dean Wakerley wrote:
> Description: The expansion of a variable containing spaces splits on all
> spaces including escaped/backslashed space.
It's not a bug, you probably want
eval ./echo_args.sh ${TCL_DEFS}
but you're sitting on very thin ice here.
--
D.
Hi bug-bash,
The Linux kernel supports creating pipes in a mode (enabled by passing
the O_DIRECT flag, and known sometimes as a "packetized pipe") that
respects message boundaries, to an extent.
An excerpt from the Linux manpage pipe(2):
O_DIRECT (since Linux 3.4)
Create
From: deanw
To: bug-bash@gnu.org
Subject: Backslashed space in variable expansion does not prevent splitting.
Configuration Information [Automatically generated, do not change]:
Machine: i686 OS: cygwin Compiler: gcc Compilation CFLAGS: -
DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE=
