2>&1 takes stderr (fd#2) and joins it to stdout (fd#1) so you have a single
output stream, contains both things sent to stderr (fatal program errors) and
stdout messages (informational or program specific messages)
> On 25 Nov 2013, at 4:30 am, Tim Streater wrote:
>
> 2>&1
---
If apache can write everything on start, and then it becomes unresponsive, that
sounds like file handles / inodes. There wont be errors as likely the thread
with the problem can't write logs..
But if apache locks up hard, due to no inodes, or something else, you wont kill
it with a kill -1, and
On 18/08/2012, at 6:46 AM, Denis BUCHER wrote:
> Dear all,
>
> That's an unbelievable issue but we have single apache process that takes 5
> GB of memory ! And it doesn't happens always with the same URLs, it's
> unpredictable and we don't understand why it is happening at all !!!
>
> Any hel
Shouln't that be :
"../../chorus-theme/css/main.css?browserId=firefox&t=1344590189623"
First non-url part is after ?, other parts seperated by &
Pretty sure @ has special meaning in a url..
On 17/08/2012, at 2:03 PM, Nicolas Maujean wrote:
> "../../chorus-theme/css/main.css@browserId=firefo
On 09/08/2012, at 1:43 PM, Liu JinGang wrote:
> ApacheGroup Mem:
>
> hello,boys~
>
> I use the deamontools to control the apache.
> run script as following(refer to the doc of www):
> -
> #!/bin/sh
>
> CONF=/etc/httpd/conf/httpd.conf
> DAEMON=/usr/sbin/h
