Their basic functionality is very similar: Read from STDIN or a file. Pipe Monitor ( github) is an alternative designed to output updates to a log stream via STDERR. Rob's answer is great for most situations, but Pipe Viewer doesn't work well in use cases where a tty isn't available, like when monitoring a mysql docker container's initialization output or when you want to log the progress to a file. It assumes a general level of proficiency with computers in general and unix in particular. I never intended to suggest that it was any kind of "official" technique that a manual jockey could fall back on. The method I suggested has been something you could do in one form or another since the first sql database was written. Meanwhile, you can monitor the file to see how a transfer is progressing. I think that it is highly unlikely that the day will dawn when a database does not involve a file somewhere or other. I noticed the transfer was taking ages and used this technique to monitor progress. I happened to use this fact recently when a long term database had built up a log file of around 20G over a period of three or four years. If there are many tables you can also watch them appear one by one in /var/lib/mysql/. This will end up the same size (or thereabouts) of the filesize in your source server. You can monitor the size of ibdata1 file in /var/lib/mysql which contains the data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |