05-11-2018
Xdm error 2817 SunOS 4.1.4 OpenWindows
Hi members!
I have installed SunOS 4.1.4 under QEMU.
I would like to use it with xdm. I launch xdm and get login window.
But when I have inputed user name and password,
XDM exited with the message:
"error (334): Unknown session exit code 2817 from process 342"
I have checked:
pid 334 is the parent process of XDM;
pid 342 is the child XDM ( 334 ->342).
------------
Also I have found a link in the internet with this issue,
but a link is down.
------------
Please, help me.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have searched the internet and this site and cannot find a way to remove CDE from a sparc Solaris 8 machine.
I could run pkgrm on the individual CDE packages but would like to know if there is a more efficient way. 2.5.1 seemed to have had an uninstall script that 8 does not.
What... (1 Reply)
Discussion started by: blp001
1 Replies
2. UNIX for Advanced & Expert Users
I have compiled binary file using "cc" on SunOS 5.8 and the same binary file i have copied to SunOS 5.9 and it is giving me core dump error.I want to know whether migration of compiled code from lower version to higer version created this problem. how can i solve this problem.I am pasting the core... (1 Reply)
Discussion started by: Arvind Maurya
1 Replies
3. Solaris
can someone hlpe me to use a X display manger to oepnsolaris
I'm using 79a & have setup XMING on a windows client
On the Solaris box I notice that XDM is not running, which i assume is essential for xming\client. I've read somewhere that to enable XDM i need to run gdmconfig so i've
# xhost+... (5 Replies)
Discussion started by: stevie_velvet
5 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I would like to change the size of the shelltool window when the full size is selected, by clicking on the top of the window.
The issue is... I have a monitor that cannot do 1152x900 resolution format. The monitor can only do 1152x870. Also the frame buffer cannot do any other resolution.... (0 Replies)
Discussion started by: Sean_69
0 Replies
5. Solaris
Hi all!
On my SPARC mashine I have changed the screen resolution from default to: output-device screen r1024x768x75, because the OBP picture too big (e.g. Sun Logo and OBP text).
Now, after the system booting I have the problem with OpenWindows picture (e.g. the window manager does not display... (2 Replies)
Discussion started by: wolfgang
2 Replies
6. UNIX for Dummies Questions & Answers
Hi all,
I have remote 2Mbs connection to server.
I am wondering - what is the difference (i mean - transferring data) between Citrix sessions and XDMCP?
Why I can connect to server using Citrix and when clicking to open some application its opening fast, but when i am clicking to open same... (0 Replies)
Discussion started by: nypreH
0 Replies
7. Solaris
Hi all,
I have remote 2Mbs connection to server.
I am wondering - what is the difference (i mean - transferring data) between Citrix sessions and XDMCP?
Why I can connect to server using Citrix and when clicking to open some application its opening fast, but when i am clicking to open same... (1 Reply)
Discussion started by: nypreH
1 Replies
8. UNIX for Dummies Questions & Answers
Hello,
We have a SunOS 5.6 system that works as a Real Time Interface to make work an engraving machine. Today we started the computer and showed the next message:
Boot device: disk:a File and args:
SunOS Release 5.6 Version Generic_105181-39
Copyright (c) 1983-2003, Sun Microsystems,... (3 Replies)
Discussion started by: hgb_flexaprint
3 Replies
9. Solaris
Hi guys, Just wondering how I can get
OpenWindows 3 window manager.
I installed SunOS 4.1.4 on Qemu
and when I type Openwin,
I will get a purpleish interface,
which I am not fond of.
I'd like to have the following look and feel...
OpenWindows 3 - SunOS 4.1.4
Thanks Jack (2 Replies)
Discussion started by: lucky7456969
2 Replies
10. Ubuntu
I'd appreciate an explanation of the ?xdm? listing under the IDLE column (see below) after I ran the 'w' command in BASH. I recently used 'umask 0022' but reset it to 'umask 0000' I can't think this would have caused the ?xdm?, but as a total novice, I'd like some help.
USER TTY FROM ... (1 Reply)
Discussion started by: hal_v_1937
1 Replies
setpgid(2) System Calls Manual setpgid(2)
NAME
setpgid(), setpgrp2() - set process group ID for job control
SYNOPSIS
DESCRIPTION
The and system calls cause the process specified by pid to join an existing process group or create a new process group within the session
of the calling process. The process group ID of the process whose process ID is pid is set to pgid. If pid is zero, the process ID of the
calling process is used. If pgid is zero, the process ID of the indicated process is used. The process group ID of a session leader does
not change.
is provided for backward compatibility only.
Security Restrictions
Some or all of the actions associated with this system call are subject to compartmental restrictions.
See compartments(5) for more information about compartmentalization on systems that support that feature. Compartmental restrictions can
be overridden if the process possesses the privilege (COMMALLOWED). Processes owned by the superuser may not have this privilege. Pro-
cesses owned by any user may have this privilege, depending on system configuration.
See privileges(5) for more information about privileged access on systems that support fine-grained privileges.
RETURN VALUE
and return the following values:
Successful completion.
Failure.
is set to indicate the error.
ERRORS
If or fails, is set to one of the following values.
The value of pid matches the process ID of a child process of the calling process and the child process has successfully executed
one of the exec(2) functions.
The value of pgid is less than zero or is outside the range of valid process group ID values.
The process indicated by
pid is a session leader.
The value of pid is valid but matches the process ID of a child process of the calling process, and the child process is not in
the same session as the calling process.
The value of pgid does not match the process ID of the process indicated by pid and there is no process with a process group ID
that matches the value of pgid in the same session as the calling process.
The value of pid does not match the process ID of the calling process or of a child process of the calling process.
AUTHOR
and were developed by HP and the University of California, Berkeley.
SEE ALSO
bsdproc(3C), exec(2), exit(2), fork(2), getpid(2), kill(2), setsid(2), signal(2), privileges(5), termio(7).
STANDARDS CONFORMANCE
setpgid(2)