https://github.com/fermi-ad/acnetd

Unix service to support the ACNET protocol

https://github.com/fermi-ad/acnetd

Science Score: 21.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
    Organization fermi-ad has institutional domain (ad.fnal.gov)
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (13.6%) to scientific vocabulary

Keywords

acnet
Last synced: 4 months ago · JSON representation

Repository

Unix service to support the ACNET protocol

Basic Info
  • Host: GitHub
  • Owner: fermi-ad
  • License: other
  • Language: C++
  • Default Branch: main
  • Homepage:
  • Size: 254 KB
Statistics
  • Stars: 1
  • Watchers: 2
  • Forks: 1
  • Open Issues: 0
  • Releases: 0
Topics
acnet
Created about 1 year ago · Last pushed 12 months ago
Metadata Files
Readme License

README.md

ACNETD Service

This project implements the ACNET daemon (acnetd) and is the implementation of the ACNET communication protocol.

Overview

The ACNETD service is responsible for managing UDP connections on the local machine and handling various tasks related to network communication. It includes classes and methods for handling external and internal tasks, managing IP addresses, and processing network commands.

Building and Running

To build and run the ACNETD service, follow these steps:

  1. Ensure you have the necessary dependencies installed.
  2. Compile the source code using your preferred C++ compiler.
  3. Run the resulting executable.

Prerequisites

  • g++
  • make
  • Standard build tools (ar, ranlib)
  • OpenSSL development libraries (-I/usr/include/openssl). If you do not have OpenSSL installed, you can follow the instructions here to download and install it.

Compilation

To compile the ACNETD service, navigate to the project directory and run:

sh make

This will generate the acnetd executable in the project directory.

CVS Synchronization Process using Git Patches

Due to our build system's reliance on CVS, we need to bridge the gap between our Git-based development workflow and CVS. This process automates the generation of patch files for each commit to the main branch in Git and provides a bash script to assist with the manual application of these patches to our CVS repository.

Prerequisites on the CVS Server

Before you can use the CVS Sync Patch script, ensure the following tools are installed on your CVS server (or the node you use to access CVS):

  • curl: For downloading patch files from GitHub Releases. (Confirmed: curl 7.76.1 is sufficient)
  • jq: For parsing JSON output from the GitHub API. (Confirmed: jq 1.6 is sufficient)
  • patch: For applying the generated patch files to your CVS working copy.
  • cvs: The CVS client to interact with your CVS repository.

GitHub Workflow Setup

The automated part of this process is handled by a GitHub Workflow defined in .github/workflows/cvs-patch.yaml.

Owner

  • Name: Fermilab Accelerator Directorate
  • Login: fermi-ad
  • Kind: organization
  • Location: United States of America

Fermilab Accelerator Systems

GitHub Events

Total
  • Watch event: 1
  • Issue comment event: 6
  • Push event: 11
  • Public event: 1
  • Pull request review comment event: 6
  • Pull request review event: 16
  • Pull request event: 14
  • Fork event: 2
  • Create event: 8
Last Year
  • Watch event: 1
  • Issue comment event: 6
  • Push event: 11
  • Public event: 1
  • Pull request review comment event: 6
  • Pull request review event: 16
  • Pull request event: 14
  • Fork event: 2
  • Create event: 8

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 0
  • Total pull requests: 8
  • Average time to close issues: N/A
  • Average time to close pull requests: about 18 hours
  • Total issue authors: 0
  • Total pull request authors: 2
  • Average comments per issue: 0
  • Average comments per pull request: 0.5
  • Merged pull requests: 5
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 8
  • Average time to close issues: N/A
  • Average time to close pull requests: about 18 hours
  • Issue authors: 0
  • Pull request authors: 2
  • Average comments per issue: 0
  • Average comments per pull request: 0.5
  • Merged pull requests: 5
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
  • beauremus (7)
  • rneswold (1)
Top Labels
Issue Labels
Pull Request Labels