Sponsored Content
Operating Systems AIX Remote printing to Linux CUPS queue Post 302527679 by tgx on Saturday 4th of June 2011 11:34:46 AM
Old 06-04-2011
There is no error generated that I can find. When I submit a print job the queue simply goes down. It seems like I had this working at one time but my notes are a bit sketchy. As for using a 14 year old OS....yes we really do and yes it is a production system. Not my choosing but the pay is the same. Smilie
 

10 More Discussions You Might Find Interesting

1. AIX

Printing multiple copies via remote queue

Hi all, I have an interesting problem. Using remote queues to print using jetdirect printers I am unable to get a printer to print multiple copies of a print job. command being used: lpr -P -#3 ./test (one copy prints) Also tried: enq -P -C3 ./test (same results) Any ideas? ... (6 Replies)
Discussion started by: Luck
6 Replies

2. Linux

Landscape printing broken in CUPS?

Hello, I am using version: cups-config --version - 1.2.4 However, when i use the -o land or -o landscape command it doesn't print in Landscape. I have the same problem on another server. (Both running CENTOS). Does landscape printing work in CUPS? Is there a fix? Thanks in an... (0 Replies)
Discussion started by: stuaz
0 Replies

3. AIX

Remote printing from Linux to AIX

Hello, I am trying to setup remote printing from a Linux machine (Red Hat 5.3) to an AIX machine (AIX 5.3). Remote printing for "normal" print jobs is working out OK, but I'm having trouble with some AIX printers that have a user defined backend. I turned on logging for lpd on the AIX... (0 Replies)
Discussion started by: sbaker
0 Replies

4. Red Hat

Remote printing from Linux to AIX

Hello, I also posted this on the AIX forum in hopes of getting help. I am trying to setup remote printing from a Linux machine (Red Hat 5.3) to an AIX machine (AIX 5.3). Remote printing for "normal" print jobs is working out OK, but I'm having trouble with some AIX printers that have a user... (0 Replies)
Discussion started by: sbaker
0 Replies

5. SCO

Printing as a CUPS client, only root can print!

Hi, i'm running Openserver 5.0.7 as a CUPS client for a Linux server. The root user can issue a "lpstat -t" to see the printers and can submit jobs without issues. The problem presents when I try to work as a regular user. If I issue an "lpstat -t" all I get after a few seconds is "lpstat:... (1 Reply)
Discussion started by: cyruspy
1 Replies

6. UNIX for Dummies Questions & Answers

Sco Unix printing : jobs hangs in queue - printing via lp versus hpnpf

Hi, We have a Unix 3.2v5.0.5. I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts). This is the configuration file : Code: root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies

7. UNIX for Advanced & Expert Users

Slow printing to network printers using CUPS

Hi Guys, I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower... (0 Replies)
Discussion started by: rudigarude
0 Replies

8. Red Hat

cups printing error

Hi All, Having searched for a solution to this issue i found no suggestions which help my particular problem. I am getting the following error message on 1 of the 3 printers i have configured: recoverable: Network host 'xxx.xxx.xxx.xxx' is busy; will retry in 30 seconds All 3 printers are... (0 Replies)
Discussion started by: Tommyk
0 Replies

9. UNIX for Advanced & Expert Users

Troubleshooting printing through Cups

Hello Experts, I have been facing an issue with printing through cups configured on Linux server. All was going on well but all of a sudden the printers started giving an error message, "Unsupported format application/postscript!" and we cant get any prints of any printer. Need your help as... (2 Replies)
Discussion started by: Rockyc3400
2 Replies

10. UNIX for Advanced & Expert Users

LPR CUPS to Windows server and queue.

Hi everyone, Our office has a lot of printers (label & laser), and sometimes it gets quite hard to configure a new printer in CUPS as most printer manufactures does not provide drivers/ppd for CUPS/LINUX/UNIX. So we are trying to move to a Windows Print Server and run a Proof of concept. We... (2 Replies)
Discussion started by: Syed Hussaini
2 Replies
GLOBUS-JOB-SUBMIT(1)						  GRAM5 Commands					      GLOBUS-JOB-SUBMIT(1)

NAME
globus-job-submit - Submit a batch job using GRAM SYNOPSIS
globus-job-submit [-dumprsl] [-dryrun] [-verify] [-file ARGUMENT_FILE] SERVICE_CONTACT [-np PROCESSES | -count PROCESSES] [-m MAX_TIME | -maxtime MAX_TIME] [-p PROJECT | -project PROJECT] [-q QUEUE | -queue QUEUE] [-d DIRECTORY | -directory DIRECTORY] [-env NAME=VALUE]... [-stdin [-l | -s] STDIN_FILE] [-stdout [-l | -s] STDOUT_FILE] [-stderr [-l | -s] STDERR_FILE] [-x RSL_CLAUSE] [-l | -s] EXECUTABLE [ARGUMENT...] globus-job-submit [-help] [-usage] [-version] [-versions] DESCRIPTION
The globus-job-submit program constructs a job description from its command-line options and then submits the job to the GRAM service running at SERVICE_CONTACT. The executable and arguments to the executable are provided on the command-line after all other options. Note that the -dumprsl, -dryrun, -verify, and -file command-line options must occur before the first non-option argument, the SERVICE_CONTACT. The globus-job-submit provides similar functionality to globusrun in that it allows batch submission of GRAM jobs. However, unlike globusrun, it uses command-line parameters to define the job instead of RSL expressions. To retrieve the output and error streams of the job, use the program globus-job-get-output. To reclaim resources used by the job by deleting cached files and job state, use the program globus-job-clean. To cancel a batch job submitted by globus-job-submit, use the program globus-job-cancel. OPTIONS
The full set of options to globus-job-submit are: -help, -usage Display a help message to standard error and exit. -version Display the software version of the globus-job-submit program to standard output. -versions Display the software version of the globus-job-submit program including DiRT information to standard output. -dumprsl Translate the command-line options to globus-job-submit into an RSL expression that can be used with tools such as globusrun. -dryrun Submit the job request to the GRAM service with the dryrun option enabled. When this option is used, the GRAM service prepares to execute the job but stops before submitting the job to the LRM. This can be used to diagnose some problems such as missing files. -verify Submit the job request to the GRAM service with the dryrun option enabled and then without it enabled if the dryrun is successful. -file ARGUMENT_FILE Read additional command-line options from ARGUMENT_FILE. -np PROCESSES, -count PROCESSES Start PROCESSES instances of the executable as a single job. -m MAX_TIME, -maxtime MAX_TIME Schedule the job to run for a maximum of MAX_TIME minutes. -p PROJECT, -project PROJECT Request that the job use the allocation PROJECT when submitting the job to the LRM. -q QUEUE, -queue QUEUE Request that the job be submitted to the LRM using the named QUEUE. -d DIRECTORY, -directory DIRECTORY Run the job in the directory named by DIRECTORY. Input and output files will be interpreted relative to this directory. This directory must exist on the file system on the LRM-managed resource. If not specified, the job will run in the home directory of the user the job is running as. -env NAME=VALUE Define an environment variable named by NAME with the value VALUE in the job environment. This option may be specified multiple times to define multiple environment variables. -stdin [-l | -s] STDIN_FILE Use the file named by STDIN_FILE as the standard input of the job. If the -l option is specified, then this file is interpreted to be on a file system local to the LRM. If the -s option is specified, then this file is interpreted to be on the file system where globus-job-submit is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. -stdout [-l | -s] STDOUT_FILE Use the file named by STDOUT_FILE as the destination for the standard output of the job. If the -l option is specified, then this file is interpreted to be on a file system local to the LRM. If the -s option is specified, then this file is interpreted to be on the file system where globus-job-submit is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. -stderr [-l | -s] STDERR_FILE Use the file named by STDERR_FILE as the destination for the standard error of the job. If the -l option is specified, then this file is interpreted to be on a file system local to the LRM. If the -s option is specified, then this file is interpreted to be on the file system where globus-job-submit is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. -x RSL_CLAUSE Add a set of custom RSL attributes described by RSL_CLAUSE to the job description. The clause must be an RSL conjunction and may contain one or more attributes. This can be used to include attributes which can not be defined by other command-line options of globus-job-submit. -l When included outside the context of -stdin, -stdout, or -stderr command-line options, -l option alters the interpretation of the executable path. If the -l option is specified, then the executable is interpreted to be on a file system local to the LRM. -s When included outside the context of -stdin, -stdout, or -stderr command-line options, -l option alters the interpretation of the executable path. If the -s option is specified, then the executable is interpreted to be on the file system where globus-job-run is being executed, and the file will be staged via GASS. If neither is specified, the local behavior is assumed. ENVIRONMENT
If the following variables affect the execution of globus-job-submit. X509_USER_PROXY Path to proxy credential. X509_CERT_DIR Path to trusted certificate directory. SEE ALSO
globusrun(1), globus-job-run(1), globus-job-clean(1), globus-job-get-output(1), globus-job-cancel(1) University of Chicago 03/18/2010 GLOBUS-JOB-SUBMIT(1)
All times are GMT -4. The time now is 10:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy