10-07-2002
Cannot Resolve Host Name
I am running LexMark MarkNetPro-3 print servers on my AIX network. All of the sudden, none of my printers will print anymore. I am getting an error message on the console:
Unable to resolve host name.
This message comes up everytime a user submits a print job.
Any Ideas?
10 More Discussions You Might Find Interesting
1. IP Networking
The problem I am facing now is that the QNX host could not ping the SCO host and vice versa. They are in the same domain, ie, 172.20.3.xx. As I am very new to Unix, I guess I must have missed out some important steps. Pls help... Thanx alot (2 Replies)
Discussion started by: gavon
2 Replies
2. UNIX for Advanced & Expert Users
Hello,
I am working on HP-UX , and in the /etc/hosts file we have setup an alias:
aa.bb.cc.dd devmach2.unix.org devmach2 devma2v
The alias devma2v does not work. Error when pinging devma2v
ping: unknown host devma2v
For devmach2 the ping works fine , returning the correct IP... (4 Replies)
Discussion started by: FunnyCats
4 Replies
3. Solaris
Hi all,
i am copying .gz files from production server to development server using
"scp" command.my requirement is after copying .gz files i want to delete old
.gz files(two days back) in development server from production server.
like this way i need to delelte .log ,.z and .dmp files... (3 Replies)
Discussion started by: krishna176
3 Replies
4. Shell Programming and Scripting
Gurus/Experts
We have a centralized UNIX/Solaris server from where we can actually ssh to all other UNIX/Solaris servers...I need to write a script that reside on this centerlized server and do FileSystem monitoring (basically run df -h or -k) of other remote servers and then send an email to me... (6 Replies)
Discussion started by: anjum.suri
6 Replies
5. UNIX for Advanced & Expert Users
I do a ssh to remote host(A1) from local host(L1). I then ssh to another remote(A2) from A1.
When I do a who -m from A2, I see the "connected from" as "A1".
=> who -m
userid pts/2 2010-03-27 08:47 (A1)
I want to identify who is the local host who initiated the connection to... (3 Replies)
Discussion started by: gomes1333
3 Replies
6. UNIX for Dummies Questions & Answers
Hello....
I have two servers, one has an empty / and the other has a subdirectory with a large number (4 gig) with many, many files. I need a way to transfer the files en masse from the server with the large number of files to the one that is essentially blank.
I don't have space on the used... (16 Replies)
Discussion started by: blaine.miller
16 Replies
7. IP Networking
Hi,
I have a weird problem.
when ever I do ping command like for example
ping unix.comI get the following message:
# ping unix.com
ping: unknown host unix.com
but when I use host the computer is able to know the host.
# host unix.com
unix.com has address 81.17.242.186
unix.com mail is... (2 Replies)
Discussion started by: programAngel
2 Replies
8. Red Hat
Hi Folks,
Could anyone please point me to the right direction as I have spent so much time on this without luck. :wall:
I have installed Bind on my CentOS 5 server for internal network. The name resolution is working from the server itself only but not from the clients.
--------------... (7 Replies)
Discussion started by: dbadmin100
7 Replies
9. Solaris
Hi All
I am having VxVm on two Solaris hosts. host1 is using disk group dgHR. right now this server went down due to hardware fault. Not I need to import this dgHR into host2 server. Please let me know the procedure for the same. (1 Reply)
Discussion started by: amity
1 Replies
10. Shell Programming and Scripting
Hi All,
Need to connect to target host and execute a command and connect back to source host to continue with next set of command execution.
Is there a utility/command using which we can connect to target host ?
Please suggest.
Note: Netezza database is instaled on Linux server. ... (4 Replies)
Discussion started by: Nagaraja Akkiva
4 Replies
cancel(1) cancel(1)
NAME
cancel - cancel print request
SYNOPSIS
cancel [ request-ID...] [destination...]
cancel -u user... [destination...]
The cancel utility cancels print requests. There are two forms of the cancel command.
The first form of cancel has two optional arguments: print requests (request-ID) and destinations (destination). Specifying request-ID with
destination cancels request-ID on destination. Specifying only the destination cancels the current print request on destination. If desti-
nation is not specified, cancel cancels the requested print request on all destinations.
The second form of cancel cancels a user's print requests on specific destinations.
Users can only cancel print requests associated with their username. By default, users can only cancel print requests on the host from
which the print request was submitted. If a super-user has set user-equivalence=true in /etc/printers.conf on the print server, users can
cancel print requests associated with their username on any host. Super-users can cancel print requests on the host from which the print
request was submitted. Superusers can also cancel print requests from the print server.
The print client commands locate destination information using the printers database in the name service switch. See nsswitch.conf(4),
printers(4), and printers.conf(4) for details.
The following options are supported:
-u user The name of the user for which print requests are to be cancelled. Specify user as a username.
The following operands are supported:
destination The destination on which the print requests are to be canceled. destination is the name of a printer or class of printers
(see lpadmin(1M)). If destination is not specified, cancel cancels the requested print request on all destinations. Specify
destination using atomic or POSIX-style (server:destination), names. See for information regarding using POSIX-style des-
tination names with cancel. See standards(5) for information regarding POSIX.
request-ID The print request to be canceled. Specify request-ID using LP-style request IDs (destination-number).
user The name of the user for which the print requests are to be cancelled. Specify user as a username.
The following exit values are returned:
0 Successful completion.
non-zero An error occurred.
/var/spool/print/* LP print queue.
$HOME/.printers User-configurable printer database.
/etc/printers.conf System printer configuration database.
printers.conf.byname NIS version of /etc/printers.conf.
printers.org_dir NIS+ version of /etc/printers.conf.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWpcu |
+-----------------------------+-----------------------------+
lp(1), lpq(1B), lpr(1B), lprm(1B), lpstat(1), lpadmin( 1M), nsswitch.conf(4), printers(4), printers.conf(4), attributes(5), standards(5)
POSIX-style destination names (server:destination) are treated as print requests if destination has the same format as an LP-style request-
ID. See standards(5).
Some print servers send cancelation notification to job owners when their print jobs have been cancelled. This notification usually comes
in the form of an email message. Cancelation notices cannot be disabled on a Solaris server.
23 Feb 2005 cancel(1)