Hello Eric,
I've solved it by set a change directory before the problematic tar command.
The suggested change will be tested tonight.
I'm using CentOS 5 latest update (5.10). Qtp:
qmailtoaster-plus-0.3.2-1.4.20
Thanks,
Peter
Oorspronkelijk bericht
Van Eric Shubert
Datum: 0
On Sunday 06 April 2014 07:17 AM, Eric Shubert wrote:
On 04/05/2014 06:33 PM, Bharath Chari wrote:
On Saturday 05 April 2014 08:33 PM, Eric Shubert wrote:
On 04/05/2014 04:44 AM, Bharath Chari wrote:
On Saturday 05 April 2014 07:38 AM, Eric Shubert wrote:
Another option (of course) is to h
On 04/05/2014 06:33 PM, Bharath Chari wrote:
On Saturday 05 April 2014 08:33 PM, Eric Shubert wrote:
On 04/05/2014 04:44 AM, Bharath Chari wrote:
On Saturday 05 April 2014 07:38 AM, Eric Shubert wrote:
Another option (of course) is to have both public and private
interfaces on any public fa
On Saturday 05 April 2014 08:33 PM, Eric Shubert wrote:
On 04/05/2014 04:44 AM, Bharath Chari wrote:
On Saturday 05 April 2014 07:38 AM, Eric Shubert wrote:
Another option (of course) is to have both public and private
interfaces on any public facing host (as many servers do), and only
allow
On 04/05/2014 11:13 AM, Peter Peterse wrote:
Hello list,
on my qtp installation the backup doesn't work any more. I don't
remember that I've change something in the script, so maybe it's an
issue one of the yum update processes.
I've trace the issue to the next command which is located in the s
Hello list,
on my qtp installation the backup doesn't work any more. I don't
remember that I've change something in the script, so maybe it's an
issue one of the yum update processes.
I've trace the issue to the next command which is located in the script:
tar -C $backupdest \
-czf $backupdes
On 04/05/2014 04:44 AM, Bharath Chari wrote:
On Saturday 05 April 2014 07:38 AM, Eric Shubert wrote:
Another option (of course) is to have both public and private
interfaces on any public facing host (as many servers do), and only
allow ssh access from the private side.
And yet another is to
On Saturday 05 April 2014 07:38 AM, Eric Shubert wrote:
Another option (of course) is to have both public and private
interfaces on any public facing host (as many servers do), and only
allow ssh access from the private side.
And yet another is to have a perimeter firewall that port forwar