topic Re: File Manager in Operating System - HP-UX

File Manager

Brian W Herriman — Tue, 01 Jul 2003 12:27:15 GMT

Good morning.

I am operating an HP-UX 10.20 system. When I open the filemanager and go to an NFS mounted directory and double-click on a file I get the following error.

The request to service this action has failed for the following reason:

TT_DESKTOP_ENOENT No such file or directory.

If it is a local file system this does not happen. Any help would be greatly appreciated.

Thanks.

Re: File Manager

Steven E. Protter — Tue, 01 Jul 2003 12:53:55 GMT

Go to the command line and run bdf.

I think you will get a delay followed by an error message about a stale nfs connection.

If I am correct and nfs connection is stale, which means connectivity has been lost since mount, probably due to the target server being booted.

The fix is to umount and mount the nfs share, assuming there is no netowrk problem preventing you from doing so.

Lets say the nfs mount is called /machine2

umount /machine2

This might fail due to open processes.

check with

fuser -cu /machine2

kill with

fuser -cuk /machine2

umount /machine2

mount /machine2

If you get an error at mount time, check /etc/fstab and general network connectivity. Start with ping.

SEP

Re: File Manager

Brian W Herriman — Tue, 01 Jul 2003 12:59:03 GMT

Thank You, However this is not the case. NFS is working properly. The file system is mounted and I can access the files manually. I can move them around, open them and edit them.
My mount options are as follows.
chpt520:disk5 /disk5 nfs rw,suid,hard,intr 0 0

could there be something I need to do with the options?

Re: File Manager

Massimo Bianchi — Tue, 01 Jul 2003 13:03:26 GMT

Hi,
i know there is a problem with DT DESKTOP and NFS mounts.

When you move or open file around graphically, you get some .nfs#### files created, and these are released only when DT DESKTOP is closed.
Deleting this files manually does not help, they get re-created.

NFS user must be able to write to this directory.

I think this might be the problem...

HTH,
Massimo

Re: File Manager

Caesar_3 — Tue, 01 Jul 2003 19:08:07 GMT

Hello!

Check the permissions of your nfs mount,
that you can write to the directory.

Caesar

Re: File Manager

Pauline Brasch — Wed, 02 Jul 2003 04:37:55 GMT

Is this directory automounted?
CDE only supports temporary mounts created by automount(1M) when created using the special map mode, -hosts

Re: File Manager

John Stiles — Wed, 02 Jul 2003 15:40:28 GMT

Brian,

It's been years since I saw this error. Had to dig to find my notes. I had help from HP.
In the following notes the # precedes comments made by me.

(1) Login under CDE (non-root user) on the HP-UX system
that has the problem.
(2) Open 2 dtterm windows.
(3) In one dtterm window, "su" to root. In this window, do the
following:

Execute:

cd /etc/dt/appconfig/types/C

ls -l #note I used the l command.
# or better to use ll dtpad.dt uxstd.dt

look for the existance of dtpad.dt and/or uxstd.dt If
either do exist, make backups for safe keeping.

Use -i option on cp, and if target file exists, answer "No";
you will edit the pre-existing file.

Execute:

cp -i /usr/dt/appconfig/types/C/dtpad.dt .
#note: I used cp -p -i to maintain permissions.

Execute:

cp -i /usr/dt/appconfig/types/C/uxstd.dt .
#note: I used cp -p -i to maintain permissions.

Edit the ./dtpad.dt file, making the following modifications:

REPLACE:

MAP_ACTION DtTTMediaOpen

WITH:

MAP_ACTION OpenDtpad

Save the ./dtpad.dt file.

Edit the ./uxstd.dt file, making the following modifications:

ADD:

ACTION OpenDtpad
{
LABEL Text Editor (Vi)
ARG_COUNT 0
WINDOW_TYPE NO_STDIO
TYPE COMMAND
EXEC_STRING /usr/dt/bin/dtpad
DESCRIPTION The Text Editor action runs the dtpad command directly without using ToolTalk
}
ACTION OpenDtpad
{
LABEL Text Editor (Vi)
ARG_CLASS FILE
ARG_COUNT >0
TYPE COMMAND
WINDOW_TYPE NO_STDIO
EXEC_STRING /usr/dt/bin/dtpad "%Arg_1%"
DESCRIPTION The Text Editor action runs the dtpad command directly without using ToolTalk
}

Save the ./uxstd.dt file.

(4) In the other dtterm window (non-root), do the following:

Close all dtpad windows.

Execute:

ps -ef |grep dtpad

Normally, 2 dtpad processes will exist for this user's
session (owned by this user). The ps output would
typically indicate this with lines that contain the
commands:

dtpad -server
/usr/bin/sh -c dtpad -server

Use "kill" to kill all dtpad processes owned by the user.

Execute:

/usr/dt/bin/dtaction ReloadActions

and wait until the FrontPanel activity light stops blinking.

Execute:

/usr/dt/bin/dttypes |grep -i OpenDtpad

and confirm the output shows grep finds "OpenDtpad"

(5) Click on the text editor Icon and see if it works with core
core dumping.

This changes the Dtpad action's MAP ACTION from the default
DtTTMediaOpen action to the (new) OpenDtpad action. The OpenDtpad
action bypasses tooltalk, and instead invokes dtpad directly.

Kinda long, hope it helps.

John