You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2011/01/10 22:41:45 UTC
[jira] Updated: (TS-16) Do we really need proxy/mgmt2/tools ?
[ https://issues.apache.org/jira/browse/TS-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-16:
----------------------------
Fix Version/s: (was: 2.1.6)
3.1
Moving this out to v3.1. Some of this has already been cleaned up, the rest probably should be moved to "lib" (lib/sysapi perhaps?)
> Do we really need proxy/mgmt2/tools ?
> -------------------------------------
>
> Key: TS-16
> URL: https://issues.apache.org/jira/browse/TS-16
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cleanup
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Priority: Trivial
> Fix For: 3.1
>
>
> These are a number of "sysadmin" style tools, I seriously doubt these are useful?
> ubuntu9-10 (02:28) 352/1 $ ls
> ConfigAPI.cc Makefile.am NetConfig.cc SysAPI.h VIPConfig.cc
> ConfigAPI.h Makefile.in NetConfig.o SysAPI.o VIPConfig.o
> ConfigAPI.o mcast_snoop* shmem_clean* time_config* vip_config_rm
> libinkconfigapi.a McastSnoop.cc ShmemClean.cc TimeConfig.cc
> libinksysapi.a McastSnoop.o ShmemClean.o TimeConfig.o
> Makefile net_config* SysAPI.cc vip_config*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.