09-11-2009
yes, if ur server do not connect to internet, then u need to install it manually and apply it to ur servers.. its really bothering me as well, but if it's possible try to open the access-list from your router to allow it download from the redhat networks for a while then close it again. actually there is no use to patch the server when the server is not connected to internet. it only will bring an disaster and screw the systems of your server which is currently working fine. stupid auditors or security team makes this thing happened.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone, I hope this is the right place to ask this question...
I have a contract to convert a mainframe/DB2 application to using AIX/Oracle. Everything went fine but we are now running into a terminal problem. With the Mainframe app, the clients had great response time from remote... (5 Replies)
Discussion started by: rocky_triton
5 Replies
2. UNIX for Advanced & Expert Users
I have a suse linux 9(SLES 9)
I have configured "YOU" (yast online update) and it all working fine, synchronising on a daily base with http://sdb.suse.de/download but I would like to know if they is a tools or scripts that inform you of any patches that has not been applied and notify you via... (0 Replies)
Discussion started by: hassan1
0 Replies
3. Linux
Does anyone know who to centrally manage the distribution and application of patches to multiple Linux platforms ? Is there software for this ? (0 Replies)
Discussion started by: jimthompson
0 Replies
4. Linux
I was wondering how everyone else manages patching/upgrades for apache.
Latest doesnt mean greatest, we typically dont install the newest patches for our OS's. We typically run 3-6 months behind, to let fixes get fixed before installing them.
Does anyone here have a written detailed plan... (0 Replies)
Discussion started by: Ikon
0 Replies
5. UNIX for Advanced & Expert Users
Does anyone know of any tools that manage the rollout of patches across multiple types of Unix platform ( eg Solaris, Aix etc ).
I am looking for something that does a similiar job to SMS or WSUS in the Windows world (3 Replies)
Discussion started by: jimthompson
3 Replies
6. Solaris
Hello Friends..
I have not tried anything related to Solaris patch and wish to learn more about it. I just wanted to try the patchadd and patchrm commands and how they work, just for educational purpose. I tried to download Solaris 10 patches, it asked me to register at sunsolve.com and i... (5 Replies)
Discussion started by: saagar
5 Replies
7. UNIX for Advanced & Expert Users
We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies
8. HP-UX
HI all,
As per the audit policy, patch has to be apply periodically, but in my scenerio, it has been applied lastly in the year 2010.
Using HP UX 11.11, 11.21 and 11.31
I would like to know, how to identify the patches which are need to update, what will be the procedure to update, how to... (5 Replies)
Discussion started by: selvaforum
5 Replies
9. Solaris
Hi Guys,
I am doing L1 Level support for Solaris Platform. Eg. User Management, File system , Print management and Job monitoring.
I recently completer my IBM Aix 7 Administration certification. Issue is that my manager is asking me do full time unix / linux patch management work for new... (5 Replies)
Discussion started by: Nats
5 Replies
PQRM(1) pqrm PQRM(1)
NAME
pqrm - Remove job from NetWare print queue
SYNOPSIS
pqrm [ -h ] [ -S server ] [ -U user name ] [ -P password | -n ] [ -C ] queue_name job_ID [ another_job_ID ... ]
DESCRIPTION
pqrm remove specified jobs from the NetWare print queue available to you on some server. If you are already connected to some server, this
one is used.
pqrm looks up the file $HOME/.nwclient to find a file server, a user name and possibly a password. See nwclient(5) for more information.
Please note that the access permissions of .nwclient MUST be 600, for security reasons.
OPTIONS
queue_name
queue_name is used to specify queue. You can not use wildcards in the name.
job_ID , another_job_ID
job_ID is used to specify which job has to be deleted.
-S server
server is the name of the server you want to use.
-U user name
If the user name your NetWare administrator gave to you differs from your unix user-id, you should use -U to tell the server about your
NetWare user name.
-P password
You may want to give the password required by the server on the command line. You should be careful about using passwords in scripts.
-n
-n should be given to mount shares which do not require a password to log in.
If neither -n nor -P are given, pqstat prompts for a password.
-C
By default, passwords are converted to uppercase before they are sent to the server, because most servers require this. You can turn off
this conversion by -C.
SEE ALSO
nwclient(5), nprint(1), slist(1), ncpmount(8), ncpumount(8), pqlist(1), pqstat(1)
CREDITS
pqrm was written by Petr Vandrovec (vandrove@vc.cvut.cz)
pqrm 03/03/1998 PQRM(1)