stale .nfs file

[V. Nyga]

Hi all,

strange problem:
My disk is nearly full - problem is a .nfs file in the user's .dt/sessionlogs dir (about 22 GB).
I found two mozilla processes of the user running at the workstation since yesterday.
One is still running, but stale file is closed some hours before now.
fuser 'file' says nothing ...

How can I find out from where this file was created? What can I check before I delete the file?

Is this (with mozilla) a known problem?
User logged out yesterday, but process is still running ...

HP-UX 11i - hw: HP C3750 - mozilla 1.2.1

Volkmar

[Robert-Jan Goossens]

Hi Volkmar,

Probable cause is the user, user did not logout correctly. Normally the processes of this user should be terminated automatically, but if seen on a lot of cases where a log file was growing when a user just shutdown his pc/workstation with the power button or lost his connection because of a network error.

You could check mozillaâ s website and check for bug reports, patches. Also check for the latest CDE patches.

Hope this helps,
Robert-

[V. Nyga]

Hi,

RJ - PPID was 1, so process was independent from user login, can't believe network error or user fault.

I tested mozilla yesterday so maybe my fault :-)
But I like to know more about possible faults and how to find the cause.

I had to delete the file now ...
But it seems like I can reproduce the fault because file grew when I started mozilla once more. But still no fuser info with this file.

Anybody an idea for what .dt/sessionlogs dir is used?

V.

[Robert-Jan Goossens]

Hi Vo,

check the $HOME/.dtprofile

Random stdout and stderr output from apps started by Session Mgr or by actions via front panel or workspace menu can be directed into the user's $HOME/.dt/sessionlogs directory. By default this output is not recorded. Instead it is sent off to /dev/null (Unix's "nothing" device).

If this random application output is wanted (usually only wanted for debugging purposes), commenting out following "dtstart_sessionlogfile" lines will send output to your $HOME/.dt/sessionlogs directory.

Alternatively, can change "/dev/null" to "/dev/console" to see this debugging output on your console device. Can start a console via the Workspace programs menu or via Application Mgr's Desktop Tools Terminal Console" icon.

Kind regards,

RJ

[V. Nyga]

Hi RJ,

$HOME/.dtprofile is normal.

One interesting point at the end of user's yesterday startlog:
logout
X connection to cadfek9:0.0 broken (explicit kill or server shutdown).
dtfile: broken pipe in PipeRead

V.

[V. Nyga]

Anyone who can tell me more?

[V. Nyga]

Anyone who can tell me more?