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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1889.0. "DECw$server_#_#error.log empty??" by DINSCO::HOULE (Steve, NM is the future!) Mon Dec 11 1989 13:03

"ever learning" decwindows is fun but frustrating sometimes.

I have the situation where all of my group's workstations have empty server
error logs but mine!
And so far I've been unable to find anything different between the systems that
would account for this difference.

I've checked the following:
  file protection/owner are the same 
  decwindows startup files seem to be the same.

Is there a startup parameter somewhere that i've missed.
Has anyone else had this problem (and knows whats going on)
THanks for your attention.  Steve
T.RTitleUserPersonal
Name
DateLines
1889.1Please mention the software version numbers...STAR::VATNEPeter Vatne, VMS DevelopmentMon Dec 11 1989 13:2811
Which version of DECwindows and VMS are you using?

In version 1, error messages from the server were not flushed out
immediately, so it is quite likely that all their error messages
are still buffered inside the server's RMS buffers.  You can test
this by generating more data for the error log until the buffer
fills and RMS writes the buffer to disk (try a connection from
an unauthorized user).

In version 2, the error messages should always be flushed out
immediately.