[Info-vax] DNFS1ACP using 100% of CPU
Sum1
not at here.com
Mon Oct 14 07:44:11 EDT 2013
On 2013-10-14 11:05:20 +0000, Sum1 said:
> On 2013-10-14 10:02:58 +0000, JF Mezei said:
>
>> On 13-10-14 04:33, Sum1 wrote:
>>
>>> ….and defining the name, system wide, as FALSE also did nothing.
>>
>> I dug up old doc and even booted VAX VMS.
>>
>> The doc confirms the creation of the log file in SYS$LOGIN. The only
>> exception is for directories where the user has no write access and for
>> the anonymous account.
>>
>> SYS$LOGIN:TCPIP$FTP_RUN.COM is what starts the FTP server when there is
>> an incoming call to port 21
>>
>> TCPIP> show serv ftp/perm/full
>>
>> Service: FTP
>>
>> Port: 21 Protocol: TCP Address: 0.0.0.0
>> Inactivity: 5 User_name: TCPIP$FTP Process: TCPIP$FTP
>> Limit: 10
>>
>> File: TCPIP$SYSTEM:TCPIP$FTP_RUN.COM
>> Flags: TCPIP
>>
>> Socket Opts: Rcheck Scheck
>> Receive: 0 Send: 0
>>
>> Log Opts: Acpt Actv Dactv Conn Error Exit Logi Logo Mdfy Rjct TimO Addr
>> File: SYS$SYSDEVICE:[TCPIP$FTP]TCPIP$FTP_RUN.LOG
>>
>> Security
>> Reject msg: not defined
>> Accept host: 0.0.0.0
>> Accept netw: 0.0.0.0
>>
>>
>>
>> I suspect the SYS$LOGIN log file is created by the actual executable
>> invoked in the FTP_RUN.COM file.
>
> That is for the server and not the client logs…different names and, in
> the client SYS$login, there can be thousands of log files, where the
> log files in FTP_RUN are limited to logsav = 2 *
> f$getsyi("cluster_nodes") + 5 versions :)
Volker…I like your thinking. Seems to have stopped creation and it
hasn't cycled around back to ;1 :)
More information about the Info-vax
mailing list