Sponsored Content
Top Forums Shell Programming and Scripting Migration unit testing process Post 302241177 by otheus on Sunday 28th of September 2008 04:39:23 PM
Old 09-28-2008
Maybe it makes sense to have ordered queries on all tables, then run the output through a filter, and finally pass it through a checksummer (md5 for instance):

Code:
<psuedocode>
For each table:
  select * from <table> order by <primary key> 
  Output query to a file. 
  Send file through a formatting filter to remove, for instance, unprintable characters and spacing. 
  Send resulting output through [b] openssl md5 - [b]

 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Process migration

Using binary translators, would it be possible capture the runtime image (instructions and data) of processes and translate these so that the process can run from where it left on a machine with a different architecture? This will be useful for migrating applications to heterogenous systems for... (3 Replies)
Discussion started by: sumona
3 Replies

2. UNIX for Dummies Questions & Answers

process migration

how can i migrate a running process in unix to another node for load balancing? (3 Replies)
Discussion started by: aisalihu
3 Replies

3. UNIX for Advanced & Expert Users

process migration

how can i migrate a running process in unix to another node? (1 Reply)
Discussion started by: aisalihu
1 Replies

4. UNIX for Dummies Questions & Answers

Testing the forking process.

Hey, first time poster and a new UNIX user here. My question is regarding the forking process. I logged in to tty1, and typed the command ls -1 and hit enter. How can i tell that the ls -1 command ran in a subshell? Thanks. (0 Replies)
Discussion started by: Vitamin254
0 Replies

5. Shell Programming and Scripting

Testing a process has ended (in the background)

Hi guys. Hopefully this question will make sense! Continuing on my script to automatically copy some huge files across the network onto various servers as background jobs, I need to be able to check that each job has finished successfully. The script below shows what I want - almost. The... (2 Replies)
Discussion started by: dlam
2 Replies

6. Red Hat

Doubt about process migration

Hello experts, My doubt is, shall we move process from one node to another node..? This will be need when the cpu running on max load. Thanks. (1 Reply)
Discussion started by: srigias
1 Replies

7. UNIX for Dummies Questions & Answers

Simple unit script

Hello guys this is my first post in this forum. Since now ive been passive an ive only been looking for existing information. Now I could use specific help on a UNIX script i want to make that would: 1. Take 1-3 arguments. 2. Display the contents of its arguments, formatted as follows:... (7 Replies)
Discussion started by: banzomaster
7 Replies

8. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
DOVEADM-INSTANCE(1)						      Dovecot						       DOVEADM-INSTANCE(1)

NAME
doveadm-instance - Manage the list of running Dovecot instances SYNOPSIS
doveadm [-Dv] [-f formatter] instance list doveadm [-Dv] instance remove name | base_dir DESCRIPTION
The doveadm instance commands are used to manage the list of Dovecot instances running on the server. In most installations there is only one Dovecot instance, but in some cases is may be useful to have more (e.g. running director proxy and backend in the same server). Instances are added to the list automatically when Dovecot is started. Each instance is uniquely identified by its base_dir setting. Instances can be named by setting instance_name in each instance's dovecot.conf. When an instance is named, it can be accessed easily by giving -i instance_name command line parameter for Dovecot binaries (e.g. doveadm). OPTIONS
Global doveadm(1) options: -D Enables verbosity and debug messages. -f formatter Specifies the formatter for formatting the output. Supported formatters are: flow prints each line with key=value pairs. pager prints each key: value pair on its own line and separates records with form feed character (^L). tab prints a table header followed by tab separated value lines. table prints a table header followed by adjusted value lines. -v Enables verbosity, including progress counter. ARGUMENTS
name The value of an instance's instance_name setting. base_dir The base directory of a Dovecot instance. COMMANDS
instance list doveadm instance list This command lists the seen Dovecot instances. instance remove doveadm instance remove name | base_dir This command removes the specified instance. REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail- able at: http://dovecot.org/bugreport.html SEE ALSO
doveadm(1) Dovecot v2.2 2012-02-16 DOVEADM-INSTANCE(1)
All times are GMT -4. The time now is 01:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy