Brian,
I am still working on getting /usr/local/spamassassin setup properly as
our primary directory with all of the components under it. Let me get a
little further on this over the next couple of days and then I think we
will be at a place where 2 sysadmins can "be in the kitchen" without
having "too many cooks in the kitchen."
At that point we can split up the components -- automc (auto masscheck),
bbmass (buildbot mass check), corpus, etc. -- and work on these in parallel.
In the meantime:
1. Setup your apache.org email address and the forwarding to your
gmail.com address at https://id.apache.org.
2. Setup your SSH key, PGP key, etc. in https://id.apache.org.
3. Setup your OPIE password so you can SSH into sa-vm1.apache.org:
https://reference.apache.org/committer/opie
4. Make sure you have the ability to "sudo su -" to become root on
sa-vm1.apache.org by using OPIE. Here is the OPIE client I am using:
https://reference.apache.org/committer/otp-md5
Dave
On 05/08/2017 10:15 AM, Kevin A. McGrail wrote:
On 5/7/2017 3:43 PM, Dave Jones wrote:
Do you know what the long-term plan is for the /x1 mount? Was it
setup as a temporary place to restore old backups?
I am trying to organize everything under /usr/local/spamassassin and
the root FS doesn't have enough space. If the plan was to eventually
unmount and give back the /x1 storage, we can do that. If we are
going able to keep it, then I would like to remount it under
/usr/local/spamassassin if that is OK.
root@sa-vm1:/usr/local/spamassassin# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 34G 8.9G 24G 28% /
/dev/sdb1 1.2T 426G 678G 39% /x1
If we need the space, use it and remount how you would like!
Regards,
KAM
