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

Conference award::copis_users

Title:COPIS VAXination Users Conference
Notice:Please use conference ORCHRD::FMAP_USERS - see note 1.1
Moderator:ORCHRD::KIPNES
Created:Wed Jul 13 1988
Last Modified:Fri May 18 1990
Last Successful Update:Fri May 02 1997
Number of topics:171
Total number of notes:402

140.0. "NETSERVER.LOG files in "home" account" by CHET::BEAUCHESNE () Wed Dec 14 1988 16:04

    I have noticed for the past few days that CINEMX is tyring to "connect"
    to my account.  The process repeats itself twice two times a day.
    
    Why is this happening, and what can I do to correct it?
    
    
    	thanks,
    	Moe
    
    NETSERVER.LOG file:
    
$ !++ 
$ ! File: SYS$MANAGER:SYLOGIN.COM
$ !--
$ set noverify          
%DCL-W-ABSYMD, abbreviated symbol definition conflict - rename symbol
%SET-W-NOTSET, error modifying HSC013$DUA100:
-CLI-E-IVDEVTYPE, invalid device type - specify a mailbox device
    
        --------------------------------------------------------

        Connect request received at 14-DEC-1988 15:36:15.88
            from remote process CINEMX::"0=BEAUCHESNE"
            for object "SYS$COMMON:[SYSEXE]FAL.EXE"

        --------------------------------------------------------

  BEAUCHESNE   job terminated at 14-DEC-1988 15:41:20.47

  Accounting information:
  Buffered I/O count:          228      Peak working set size:   419
  Direct I/O count:            154      Peak page file size:     990
  Page faults:                 942      Mounted volumes:           0
  Charged CPU time:     0 00:00:02.15   Elapsed time:     0 00:05:17.73
T.RTitleUserPersonal
Name
DateLines
140.1no cause for alarmCINEMX::KIPNESKen 269-2269Wed Dec 14 1988 16:5213
	 Maurice,

	    We have been running a process to check out the existence
	 of PROXYs on the user's home nodes.  This process then
	 updates the User Profile database which allows you to copy
	 files from ORCHRD using the Reporting and Extract facilities.

	    In the future, we will send out an informational message
	 ahead of time, so that you will be aware of this process.
	 Sorry for any confusion.

	 /ken