09-23-2004
Xmanager
hi everybody
want to access a SOLARIS system with an X Client ( or server ) ( Called Xmanager)...i think all xclients opearate the same way.
Problem : i have the error Xdmcp connection failed when i launch it!
help please!
PS: all i have done is just giving Xmanager the IP of the Sun system and taping on the sun syst:
- setenv DISPLAY IP_of_my_PC:0.0
- export DISPLAY
regards
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
I am a real newbie to this so forgive me if I ask anything which may sound silly. I have a SunFire V1120 installed with Solaris 8 on it. I have Xmanager loaded onto my pc and i want to use this to connect to this box. However Xmanager doesn't recognise the box, but I can telnet to it no... (1 Reply)
Discussion started by: joe27
1 Replies
2. UNIX for Dummies Questions & Answers
***** I running Solaris 9 and Xmanager 2.0 *****
Hey guys,
Newbie question... I'm trying to get HP OpenView's X Windows GUI to load on my WinXP machine. I know another guy at work is running Xmanager 1.3 (I have 2.0) and when he types ovw& on the server it loads the OpenView GUI on his... (4 Replies)
Discussion started by: kingdbag
4 Replies
3. Linux
I am unable to view the GUI mode of the Fedora Linux machine through the Xmanager. I don't have issues in viewing my Solaris boxes. Please let me know if anything needs to be done about this? (3 Replies)
Discussion started by: chrisanto_2000
3 Replies
4. UNIX for Dummies Questions & Answers
In the Xbrowser window, under status column, i see the following:
2 users, load: 3.7, 3.7, 3.7
What does "load" mean exactly, and the three numbers?
Thanks! (4 Replies)
Discussion started by: Deanne
4 Replies
5. Linux
For remote console logging purpose we use X-manager for Solaris environment. How X-manager config for Linux systems. I want to get Linux desktop to remote pc. that is not ssh or telnet.
Please help me. (0 Replies)
Discussion started by: saga499
0 Replies
6. Shell Programming and Scripting
hello all
i created a login scrip and add it successfully to .profile
now i need to force this .profile to be executed if the user login using xmanager not a normal telnet
best regards
---------- Post updated at 09:05 AM ---------- Previous update was at 03:25 AM ----------
Ant updates ???? (10 Replies)
Discussion started by: islam.said
10 Replies
7. HP-UX
Hello all,
please can you help me to configure XManager XDMCP connection so i can connect to my HP-UX OS.
Regards, (6 Replies)
Discussion started by: beayni33
6 Replies
8. Solaris
Hi!
I have a m3000 server with solaris 10. Clients connecting to server using Xmanager. But when they open a Java based application its very slow and some times hanging. But when I tried with VNC it works fine. Is this a BUG in Xmanager? Or Is there any method to solve this?
Thanks,
Charith (3 Replies)
Discussion started by: charith.upendra
3 Replies
9. AIX
Hello,
Oracle PDF reports run only when you run the command
# xhost +
from the console,
but if you run from the xmanager session , then report doesn't work
running from windows pc using xmanager
# xhost +
access control disabled, clients can connect from any host
# echo... (7 Replies)
Discussion started by: filosophizer
7 Replies
10. Solaris
I am trying to connect via Xmanager 4 to a T4-2 server running Solaris 11.
I checked the /etc/gdm.custom.conf file.
The error I get is
The MAC (Message Authentication Code) of packet is incorrect
When I start the Xmanager on soalris I get a message
/dev/fb (file or directory) does not... (2 Replies)
Discussion started by: Maqsood Mohamme
2 Replies
LEARN ABOUT REDHAT
qmail-queue
qmail-queue(8) System Manager's Manual qmail-queue(8)
NAME
qmail-queue - queue a mail message for delivery
SYNOPSIS
qmail-queue
DESCRIPTION
qmail-queue reads a mail message from descriptor 0. It then reads envelope information from descriptor 1. It places the message into the
outgoing queue for future delivery by qmail-send.
The envelope information is an envelope sender address followed by a list of envelope recipient addresses. The sender address is preceded
by the letter F and terminated by a 0 byte. Each recipient address is preceded by the letter T and terminated by a 0 byte. The list of
recipient addresses is terminated by an extra 0 byte. If qmail-queue sees end-of-file before the extra 0 byte, it aborts without placing
the message into the queue.
Every envelope recipient address should contain a username, an @ sign, and a fully qualified domain name.
qmail-queue always adds a Received line to the top of the message. Other than this, qmail-queue does not inspect the message and does not
enforce any restrictions on its contents. However, the recipients probably expect to see a proper header, as described in qmail-header(5).
Programs included with qmail which invoke qmail-queue will invoke the contents of $QMAILQUEUE instead, if that environment variable is set.
FILESYSTEM RESTRICTIONS
qmail-queue imposes two constraints on the queue structure: each mess subdirectory must be in the same filesystem as the pid directory; and
each todo subdirectory must be in the same filesystem as the intd directory.
EXIT CODES
qmail-queue does not print diagnostics. It exits 0 if it has successfully queued the message. It exits between 1 and 99 if it has failed
to queue the message.
All qmail-queue error codes between 11 and 40 indicate permanent errors:
11 Address too long.
31 Mail server permanently refuses to send the message to any recipients. (Not used by qmail-queue, but can be used by programs offering
the same interface.)
All other qmail-queue error codes indicate temporary errors:
51 Out of memory.
52 Timeout.
53 Write error; e.g., disk full.
54 Unable to read the message or envelope.
55 Unable to read a configuration file. (Not used by qmail-queue.)
56 Problem making a network connection from this host. (Not used by qmail-queue.)
61 Problem with the qmail home directory.
62 Problem with the queue directory.
63 Problem with queue/pid.
64 Problem with queue/mess.
65 Problem with queue/intd.
66 Problem with queue/todo.
71 Mail server temporarily refuses to send the message to any recipients. (Not used by qmail-queue.)
72 Connection to mail server timed out. (Not used by qmail-queue.)
73 Connection to mail server rejected. (Not used by qmail-queue.)
74 Connection to mail server succeeded, but communication failed. (Not used by qmail-queue.)
81 Internal bug; e.g., segmentation fault.
91 Envelope format error.
SEE ALSO
addresses(5), envelopes(5), qmail-header(5), qmail-inject(8), qmail-qmqpc(8), qmail-send(8), qmail-smtpd(8)
qmail-queue(8)