You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@singa.apache.org by "zhaiyantang (JIRA)" <ji...@apache.org> on 2015/10/16 12:30:05 UTC

[jira] [Created] (SINGA-92) Symlink log file should not exist if new destination file isn't created

zhaiyantang created SINGA-92:
--------------------------------

             Summary: Symlink log file should not exist if new destination file isn't created
                 Key: SINGA-92
                 URL: https://issues.apache.org/jira/browse/SINGA-92
             Project: Singa
          Issue Type: Improvement
            Reporter: zhaiyantang
            Priority: Minor


0-cifar10-convnet-error-20151016-105701.18749  
0-cifar10-convnet-fatal-20151016-105701.18749  
0-cifar10-convnet-info-20151016-105700.18749  
0-cifar10-convnet-warn-20151016-105701.18749  
1-cifar10-convnet-error-20151016-113248.19533  
1-cifar10-convnet-fatal-20151016-113248.19533  
1-cifar10-convnet-info-20151016-113247.19533  
1-cifar10-convnet-warn-20151016-113248.19533  
2-cifar10-convnet-error-20151016-114559.3862  
2-cifar10-convnet-info-20151016-114558.3862  
2-cifar10-convnet-warn-20151016-114559.3862  
job-info/  
lt-singa.ERROR -> 2-cifar10-convnet-error-20151016-114559.3862
lt-singa.FATAL -> 1-cifar10-convnet-fatal-20151016-113248.19533
lt-singa.INFO -> 2-cifar10-convnet-info-20151016-114558.3862
lt-singa.WARNING -> 2-cifar10-convnet-warn-20151016-114559.3862

The file 2-cifar10-convnet-fatal-20151016-114558.3862 was not created since there was no any fatal log. I think the symlink file lt-singa.FATAL should not exist instead of linking to the old file because it may give user a false impression.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)