[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9663.0. "Problems with dxdevices tool" by sloppp1port2.slo.dec.com::Mitchell Brown ([email protected]) Tue Apr 29 1997 19:25

Is there better documentation for the dxdevices tool?

I'm trying to add an X display using dxdevices, and can't seem to figure out 
the right syntax to use for the display name and devices.

What I've done is this:

1.  I entered the workstation's IP address to the /etc/hosts file
	10.1.1.10 curly
2.  I ran dxdevices and entered the following for the device name: 
	curly:0
3.  I clicked on the X display option.
4.  It brought up the options screen, and I entered the same in the devices
    box:
	curly:0
5.  I click on OK.

dxdevices core dumps.

I fiddled with several different syntax styles, and I either got a core dump, 
or I got an error message saying there was an error writing to the ttys 
database, check permissions, etc.  I wound up having to use edauth to remove 
the entry from devaccess.db, but nothing had been added to ttys.db

I read the notes that suggest using echo | edauth to add the entries.  This 
didn't work.  It added the entry just fine to the devaccess, but gave me the 
same permissions error when I tried to add the line to the ttys.db.

I did manage to get this to work by editing ttys and devaccess, entering the 
lines, and running convauth -d tv .  However, I am reluctant to tell the 
customer that he can't use either of the two "official" methods...

Thanks for your help!

Mitch
[email protected]
T.RTitleUserPersonal
Name
DateLines
9663.1NNTPD::"[email protected]"Ann MajeskeWed Apr 30 1997 12:5335
First, you didn't state what version of Digital UNIX you are using or
what version your customer is using.  the dx* tools for Enhanced security
are different between versions.

Second, you didn't give the specific command(s) you used or the exact error 
message you got when you tried to use edauth to edit the ttys file.  (Of 
course this does at least tell me that you are using a V4.0* variant, since 
edauth is not available for v3.2* variants.  But, it doesn't tell me what 
version your customer is using).

Third, the method you used to make the changes to the ttys and devassign
databases (edit the text files and use convauth) is perfectly valid for
V4.0* releases of Digital UNIX.  If you have your customer do a 
"convauth -O -d tv" first he won't lose any other changes that he's made 
to those databases in the mean time.

Fourth, I came across another workaround in my old mail that might help:
    "There is something of a workaround, although it still won't allow
    you to create X devices.  However, you can do the following:
	# /tcb/bin/edauth -dt -s <<\X
	*\:*:\
		:t_devname=*\:*:t_lock@:t_login_timeout#0:t_xdisplay:\
		:chkent:
	X
	# /tcb/bin/edauth -dv -s <<\X
	*\:*:\
		:v_devs=*\:*:v_type=xdisplay:chkent:
	X
    This gives you wildcarded X displays, which (assuming some
    discretion in what's allowed past XDMCP) should be what the
    customer really wanted anyway."

Last, these are known problems and the fixes will be in a future 
release.
[Posted by WWW Notes gateway]
9663.2V4.0B, Known Problems?sloppp1port2.slo.dec.com::Mitchell Brown[email protected]Wed Apr 30 1997 19:1111
Sorry about not including enough information.

The customer is using V4.0B.

When you say "these are known problems", are you referring to using dxdevices 
to add X terminals?

Thanks

Mitch

9663.3BothNNTPD::&quot;[email protected]&quot;Ann MajeskeThu May 01 1997 11:528
Both problems that you reported in your original note:  1) using dxdevices
to add x terminals to the ttys database; and 2) using edauth to add x
terminals
to the ttys database; are known problems and will be fixed in a future
release.
The edauth workaround I included in .1 works because it is adding wildcarded
x terminals instead of specific x terminals.
[Posted by WWW Notes gateway]