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

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

268.0. "Questions 'Bad file' en 'Error 0'." by UTROP1::RIJSBERGEN_M (Marcel Rijsbergen @uto) Wed May 25 1994 15:51

    Q1:
    
    Sometimes when a 'connection lost' occurs another messages comes up
    too.
    'Bad file number'
    
    Q2:
    
    What does 'Error 0 occurred' message mean.
    
    
    Any explanation or pointers to apporpriate documentation apreciated.
T.RTitleUserPersonal
Name		DateLines
268.1OPG::PHILIPAnd through the square window...Wed May 25 1994 16:3119
Marcel,

  Doing a "man errno" tells me that 'Bad file number' (EBADF) means...

          Either a file descriptor refers to no open file or a read request
          is made for a file that is open only for writing. Likewise, a write
          request made to a file open only for reading causes this error.
  
  I would summarize that your console connection has gone away, this has been
  detected the next time that the daemon has issued a read or write operation,
  the way it is detected is via this error returned from the call. Its nothing
  to worry about so long as the connection gets reestablished the next time
  the reconnect interval has passed.

  The 'Error 0 occured' means we got a failed status value from a system call,
  but, errno was set to 0. This is nothing to worry about.

Cheers,
Phil
268.2Thanx for explanation, but...UTROP1::RIJSBERGEN_MMarcel Rijsbergen @utoThu May 26 1994 09:4519
    Phil,
    
    Thanx for explanations, but...
    
    When the 'Bad file number' occurs the icon is grey-ed and cannot be
    used until the next check for line availability (as you mentioned). But
    using the command
    # telnet 'terminalserver' 'listener port'
    will connect you to the console of the system with the problem and you can
    work. Apparently CM is more picky about timeouts than telnet. This
    error is only happening with one site where other sites do not have any
    problems.
    
    Q: 
    Is there a (user selectable) way to up the timeout for those telnet
    console lines which have a bit more network problems so CM takes a bit
    more time before telling that the connection is lost ?
    
    Regards, Marcel.
268.3OPG::PHILIPAnd through the square window...Thu May 26 1994 10:4210
Marcel,

  It could be that PCM has timed out the connection, but the IP link is
  OK by the time you do your TELNET command, however, PCM still has to
  wait for its next check timer to go off before it attempts to reconnect.

  And no, there is no way to modify the period between reconnect attempts.

Cheers,
Phil