AIX user administration - queue management


 
Thread Tools Search this Thread
Operating Systems AIX AIX user administration - queue management
# 1  
Old 02-24-2016
CPU & Memory AIX user administration - queue management

Dear All

Please how can I create a user which would be only able to manage queue printer like creating, release, hold etc a printer queue. He would for example be able to enter commands like :

- lpstat -pprintqueue where printqueue is an existing queue on the server

- enable printqueue where printqueue is an existing queue on the server

- lp -dprintqueue where printqueue is an existing queue on the server

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

AIX Administrator - User Profile Management

Good afternoon all, Was un-sure on where to post this so I thought I would use this topic... I was wondering what best practice people use for the deletion of user profiles on AIX systems? At the moment, I currently don't delete any user profiles, they are just disabled as they... (1 Reply)
Discussion started by: SteveCPayne
1 Replies

2. AIX

User/group management in AIX

We have an environment of around 50 AIX LPARs. We use scripts for user and group account management but it is starting to get unwieldy to document and manage the accounts. It would be doable with scripts but before we dedicate resources to that, I was wondering if there is any product that you... (2 Replies)
Discussion started by: wilford
2 Replies

3. AIX

Questions on AIX 7 Administration

Here i have a question about AIX 7 Administration test. I just want the explanation: The cfgmgr command appears to be taking an excessive time to complete. The administrator was able to quit the command and return to the command prompt. The administrator does not have access to themanaging HMC and... (1 Reply)
Discussion started by: edwardz
1 Replies

4. Shell Programming and Scripting

User administration

Dear All, I need to restrict the users in our server. 1.History & history -c command working all groups & others.So i need to restrict history -c option for groups & others . 2.Any option available to view user activity with all Eg--->user1 Jul22 10:20:11 date 3.Any other Special... (7 Replies)
Discussion started by: kpoobathi
7 Replies

5. Solaris

Solaris User Administration

unable to run smgroup / smadd command to create or modify the users and directories. (1 Reply)
Discussion started by: sendhils13
1 Replies

6. Solaris

Solaris User Administration

Hi All..... How many maximum no of users can be created in solaris 10.0 Waiting for the reply ..... (2 Replies)
Discussion started by: sendhils13
2 Replies

7. Solaris

user administration

hi ' i am creating a primary group and a secondary group for a user. #groupadd -g 101 test #groupadd -g 102 test1 #useradd -d /export/home/user1 -m -s /bin/ksh -g test -G test user1 in /etc/passwd i can find the username as user1 and group name as test and where can i find the... (4 Replies)
Discussion started by: madhudeepan
4 Replies

8. UNIX for Dummies Questions & Answers

Basic Aix Administration Questions...

Would this be the right forum to ask basic unix administration questions relating to smitty tasks, etc? (2 Replies)
Discussion started by: NycUnxer
2 Replies

9. UNIX for Dummies Questions & Answers

User Administration

I have an application that runs on Unix and the user administration is managed at a Unix level. The application has an application ID which is linked to the user ids which are created at Unix level. Can you please help if I can be able to track which user used the Application ID and what action was... (0 Replies)
Discussion started by: Kopano
0 Replies
Login or Register to Ask a Question
lpq(1)							      General Commands Manual							    lpq(1)

Name
       lpq - spool queue examination program

Syntax
       lpq [ options ] [ job #...  ] [ user...	]

Description
       The  command  examines  the  spooling  area used by for printing files on the printer, and reports the status of jobs.  The command invoked
       without any arguments reports on any jobs currently in the default queue.

       When jobs are being printed, reports the queue as being ``active''.  For each job submitted, reports the user's name, current rank  in  the
       queue,  the names of files comprising the job, the job identifier and the total size in bytes.  The job identifier is a number which may be
       supplied to to remove a specific job.

       Job ordering is determined by the FIFO (First In, First Out) algorithm used to scan the spooling  directory.   When  the  queue	is  empty,
       reports that there are ``no entries''.

       File  names  may  be unavailable for some jobs, for example, if the command is used without specifying a file name, or if is used in a pipe
       line.  If file names are unavailable, the file name reported by is ``standard input''.

Arguments
       job #...    Causes to report on only the job number(s) specified.

       user...	   Causes to report on only the jobs for the specified user(s).

Options
       +n   Scan and display the spool queue until the queue is empty.	The queue is scanned every n seconds, if  no  argument	is  specified  the
	    queue is scanned every 30 seconds.

       -l   Display the status of each job on more than one line if necessary.	If this option is not used, the status of each job is displayed on
	    one line.

       -Pprinter
	    Report the status of the spool queue for the printer specified.  If this option is not used, the spool  queue  displayed  is  the  one
	    defined by the PRINTER environment variable.  If a queue is not defined by the PRINTER environment variable, the spool queue displayed
	    is for the printer named ``lp'' in the file.

Restrictions
       The displayed status of the spool queue may not always be the current status.  This is because jobs may be completed after  the	queue  has
       been examined, but before the status has been displayed.

Error Messages
       Two of the most common error messages from are:

       Warning: no daemon present (R)
       A daemon is not available for the specified printer.  Refer to the command to find out how to restart the printer daemon.

       unknown printer (R)
       The printer specified as an argument to the -P option, doesn't have an entry in the file.

Files
       For manipulating the screen for repeated display

       To determine printer characteristics

       The spooling directory, as determined from printcap

       Control files specifying jobs

       The lock file to obtain the currently active job

See Also
       lpr(1), lprm(1), lpc(8), lpd(8)

																	    lpq(1)