FreshPorts cheat sheet

This is a cheat sheet for FreshPorts behind-the-scenes administration. If you want one for users, please start with suggested content.

Ingress Actions

  1. – Take a commit from the repo and insert it into the database. Will fail if commit is already there. REPO is one of src, ports, doc. Hash is the git commit has.
    /usr/local/libexec/freshports/ REPO HASH
  2. See

  3. process vuxml – This will invoke vuxml processing of whatever is checked out into the cd ~freshports/ports-jail/var/db/repos/PORTS-head/ working copy of the ports. Tree. It might also work on the ~freshports/ports-jail/var/db/repos/ports (git) repo, but I don’t know how it tells which one to work on.
    echo touch /var/db/freshports/signals/vuxml /var/db/freshports/signals/job_waiting | sudo su -fm freshports

    Ahh, it knows based on VULNFILE=”${FRESHPORTS_JAIL_BASE_DIR}${PORTSDIR}/security/vuxml/vuln.xml”.

  4. – refreshes the Latest Vulnerabilities box of the website.
    echo /usr/local/bin/perl /usr/local/libexec/freshports/ | sudo su -fm freshports
  5. Archive messages from 11 days ago
    echo /usr/local/libexec/freshports/ 11 | sudo su -fm freshports

Ingress Services

  1. ingress – processes git commits into XML
  2. ingress_svn – processes subversion commits into XML
  3. freshports – processes the XML and loads them into the database


  • NOTIFY port_updated; – issue this command within the database. The fp_listen daemon will wake up, read the table cache_clearing_ports, and clear the cache for the listed port.
Website Pin Facebook Twitter Myspace Friendfeed Technorati Digg Google StumbleUpon Premium Responsive

Leave a Comment

Scroll to Top