Hi,
>> Your ssh isn't exiting because a child process, in this case zimbra,
>> remains. As some others have suggested, this is due to ssh waiting on both
>> stdin and stdout of the child process to close.
> or, more clear, for *any process* that has the pseudo tty allocated by ssh
> opened to c
Hi,
Stephen Joyce wrote on 11.09.2007 um 15:15:07 [Re: [BackupPC-users] Not ending
DumpPostUserCmd]:
> Your ssh isn't exiting because a child process, in this case zimbra,
> remains. As some others have suggested, this is due to ssh waiting on both
> stdin and stdout of the ch
Your ssh isn't exiting because a child process, in this case zimbra,
remains. As some others have suggested, this is due to ssh waiting on both
stdin and stdout of the child process to close.
For example, if you do the following, you'll experience a hang:
pc1$ ssh pc2
pc2$ xterm &
pc2$ log
Le jeudi 6 septembre 2007, Tobias Brunner a écrit :
evening,
[...]
> echo "Stopping time: $my_time" >> /opt/zimbra/backup/zm_backup-$my_date.log
> su - zimbra -c "/opt/zimbra/bin/zmcontrol stop" | tee -a
my guess is around the stdout and error redirections,
i think they are not close properly by
Hi,
On 11/09/2007, Tobias Brunner <[EMAIL PROTECTED]> wrote:
[...]
> > Starting stats...Done.
> > Successfully started Zimbra at 01:25:22
> >
> > That looks ok, except that the script does not end...
> > Does anyone have an idea why that is?
Maybe try to pass the -n option to ssh? Sometimes
Hi
Does no one have an idea?
Are more informations needed?
I appreciate any help...
Thanks!
Regards,
Tobias
Tobias Brunner wrote:
> Hi everybody
>
> On one server, I have DumpPostUserCmd configured to execute a script. This is
> executed after the backup, but it doesn't end so the backup can
Hi everybody
On one server, I have DumpPostUserCmd configured to execute a script. This is
executed after the backup, but it doesn't end so the backup can never finish.
Detailed description:
The DumpPreUserCmd ($sshPath -q -x -l root $host
/usr/local/bin/zimbra_pre_back.sh) stops the mailserver
