commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Oberhuber (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NET-200) UnixFTPEntryParser treats block and character devices as files
Date Tue, 08 Apr 2008 18:59:24 GMT

    [ https://issues.apache.org/jira/browse/NET-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586930#action_12586930
] 

Martin Oberhuber commented on NET-200:
--------------------------------------

Or, is there a case for more differentiation e.g.   FTPFile#DEVICE_TYPE / FTPFile#PIPE_TYPE
/ FTPFile#SOCKET_TYPE and the like ? I'd guess that an FTP client can never make much use
of these kinds of filesystem nodes anyways... although a cat /proc/meminfo is often useful
on Linux, so perhaps at least character special files should be treated as files?

> UnixFTPEntryParser treats block and character devices as files
> --------------------------------------------------------------
>
>                 Key: NET-200
>                 URL: https://issues.apache.org/jira/browse/NET-200
>             Project: Commons Net
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Sebb
>            Priority: Minor
>
> The UnixFTPEntryParser currently treats block and character devices as files; this seems
wrong.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message