for the replica catalog and the file server elements closing elements are generated.
they dont need to be and can be closed in the starting element

<site handle="CIT_CMS_T2" arch="x86" os="LINUX" osrelease="" osversion="" glibc="">
<grid type="gt2" contact="cit-gatekeeper.ultralight.org/jobmanager-fork" scheduler="Fork" jobtype="auxillary"/>
<grid type="gt2" contact="cit-gatekeeper.ultralight.org/jobmanager-condor" scheduler="Condor" jobtype="compute"/>
<head-fs>
<scratch>
<shared>
<file-server protocol="gsiftp" url="gsiftp://cit-gatekeeper.ultralight.org" mount-point="/raid2/osg-data/engage/tmp/cit-gatekeeper.ultralight.org">
</file-server>
<internal-mount-point mount-point="/raid2/osg-data/engage/tmp/cit-gatekeeper.ultralight.org"/>
</shared>
</scratch>
<storage>
<shared>
<file-server protocol="gsiftp" url="gsiftp://cit-gatekeeper.ultralight.org" mount-point="/raid2/osg-data/engage/tmp/cit-gatekeeper.ultralight.org">
</file-server>
<internal-mount-point mount-point="/raid2/osg-data/engage/tmp/cit-gatekeeper.ultralight.org"/>
</shared>
</storage>
</head-fs>
<replica-catalog type="LRC" url="rlsn://dummyValue.url.edu">
</replica-catalog>
<profile namespace="env" key="GLOBUS_LOCATION" >/opt/osgwn1.2.4/globus</profile>
<profile namespace="env" key="LD_LIBRARY_PATH" >/opt/osgwn1.2.4/globus/lib</profile>
<profile namespace="env" key="app" >/raid1/osg-app/engage</profile>
<profile namespace="env" key="data" >/raid2/osg-data/engage/tmp/cit-gatekeeper.ultralight.org</profile>
<profile namespace="env" key="tmp" >/raid2/osg-data/engage/tmp/cit-gatekeeper.ultralight.org</profile>
<profile namespace="env" key="wntmp" >/wntmp</profile>
</site>