From 573d6e9a9fc66a32d31a8780460df22f48d4588b Mon Sep 17 00:00:00 2001 From: dpage Date: Tue, 6 Jan 2009 10:01:56 +0000 Subject: [PATCH] Document how to figure out the hostname used to target job steps to a server. git-svn-id: svn://svn.pgadmin.org/trunk/pgadmin3@7538 a7884b65-44f6-0310-8a51-81a127f17b15 --- docs/en_US/pgagent-jobs.html | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/docs/en_US/pgagent-jobs.html b/docs/en_US/pgagent-jobs.html index 3d76e6b8b..0495f104b 100644 --- a/docs/en_US/pgagent-jobs.html +++ b/docs/en_US/pgagent-jobs.html @@ -29,10 +29,20 @@ details of each run of the job.

schedules. When configuring a job, we specify the job name, whether or not it is enabled, a job class or category, and optionally the hostname of a specific machine running pgAgent, if this job should only run on -that specific server. If left empty, any server may run the job. This -is not normally an issue for SQL-only jobs, however any jobs with -batch/shell steps may need to be targetted to a specific server. A -comment may also be included.

+that specific server. If left empty (which is normally the case), any +server may run the job. This is not normally needed for SQL-only jobs, +however any jobs with batch/shell steps may need to be targetted to a +specific server. A comment may also be included.

+ +

Note: It is not always obvious what value to specify for the +Host Agent in order to target a job step to a specific machine. With pgAgent +running on the required machines and connected to the scheduler database, +the following query may be run to view the hostnames as reported by each +agent:

+ +

SELECT jagstation FROM pgagent.pga_jobagent

+ +

Use the hostname exactly as reported by the query in the Host Agent field.

Job properties

-- 2.39.5