forums › forums › SQLyog › Using SQLyog › Sqlyog And Shells
- This topic is empty.
-
AuthorPosts
-
-
September 14, 2009 at 8:50 am #11674Junk1958Member
Hi All –
We are experiencing the following. Is there a switch I can use so this does not occur?
SQLyog backup/export under the Tables menu starts the Export Data As Batch Script Wizard.
For historical reasons, we must export each table separately. Most tables are exported once/day, but some are exported every 30 or 60 mins.
However, we have found that SQLyog leaves one bash.exe running on the server for each table exported (as set up in the SQLyog client). This is true even though at the end of the export we reach the screen saying “The Wizard Completed Successfuly”.
This becomes a problem because each bash.exe stays alive forever on the server – even when the SQLyog client and the client machine are shut down.
The result is that over time (in our case, 2 days) this exahusts all the pty's on the server and no new SSH tunneling connections can be made until at least one of the previous bash.exe's is killed first. Even then, you can make only as many connections as you have killed.
Also, each bash.exe requires approx 4MB memory on the server, so that memory usage on the server climbs over time. Except when the bash.exe's are all killed; then memory usage drops to normal until SQLyog runs its next export job and creates more bash.exe's that run in the background, consuming memory.
Is there a switch we should be setting in SQLyog to avoid this? Here is what we are running:
Windows 2003
SQLyog Enterprise trial v8.14
MySQL 4.1.x (where x == 22 I think) community version (I can get x if needed)
OpenSSH & bash.exe – whatever versions are being supplied by Cygwin currently (within the past week). I can get these if needed, but I am hoping the problem is not this deep into the system.
Thanks and best.
Priscilla
-
-
AuthorPosts
- You must be logged in to reply to this topic.