Re: [tor-relays] Trouble Running Middle Relay On Google Cloud Debian VBS

Subject: Re: [tor-relays] Trouble Running Middle Relay On Google Cloud Debian VBS

From: Keifer Bly <keifer.bly@xxxxxxxxx>

Date: Sat, 18 May 2019 11:40:19 -0700

Delivery-date: Sat, 18 May 2019 16:36:52 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=hXQzyLzO/YDRfcBmtfIF+GOq2qpceeQGIfxb3vp0yNc=; b=Gm4KdFNpPF7QlPDVaBdXZuF91QetZVfaDpwY5TuGiZfQILM93oE/9j303jvkltXWDr VBxcODC4aebFoB5WYI3v3EQY5I7B4+yrG3JFs34wefo/oBhBrqiuydUakA1Ped8loMbC Aoicf7vM6aBsSsA+dEhkwjqhU2UEsx+vjUre/kdJeivzUM4VjRCR/Y0gDssA8muyeDqQ tKDqpS8zOil7E0XQ3f1HBeTIxpplvScNLqdPPS+d5esUx8yJWKb5Eoq7WLD2xKkW6xMG 3+5NtFZLlYzDNHBGQzDdLHfsCoXmB30a7N4jcDDCqfW+VLvQik1iZJTugARX3Fau5V58 Ut0A==

In-reply-to: <CADqUGANqwTV9xSH+zsejisj7DaZnNQ=gZcRDyWUv5RQfaODXQQ@mail.gmail.com>

List-archive: <http://lists.torproject.org/pipermail/tor-relays/>

List-help: <mailto:tor-relays-request@lists.torproject.org?subject=help>

List-id: "support and questions about running Tor relays \(exit, non-exit, bridge\)" <tor-relays.lists.torproject.org>

List-post: <mailto:tor-relays@lists.torproject.org>

List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=subscribe>

List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-relays>, <mailto:tor-relays-request@lists.torproject.org?subject=unsubscribe>

References: <CADqUGAMe5ixz_Gk0Spdc2T5fKcmZHGwv2Cxz9HxQbpfNHJC9VQ@mail.gmail.com> <d4df844f606ccee5160fdbfc9cf1472d@neelc.org> <1289536b3d0ffe84d69f55f7cca5b6f2@for-privacy.net> <CADqUGANqwTV9xSH+zsejisj7DaZnNQ=gZcRDyWUv5RQfaODXQQ@mail.gmail.com>

Reply-to: tor-relays@xxxxxxxxxxxxxxxxxxxx

Sender: "tor-relays" <tor-relays-bounces@xxxxxxxxxxxxxxxxxxxx>

Oh sorry. What it actually says is everything is already up to date. So I wonder, why would the relay not appear in the consensus? Thanks.

--Keifer

On Sat, May 18, 2019 at 11:23 AM Keifer Bly <keifer.bly@xxxxxxxxx> wrote:

> on Debian:

apt-get install -y unattended-upgrades apt-listchanges
cp /usr/share/unattended-upgrades/20auto-upgrades
/etc/apt/apt.conf.d/20auto-upgrades
service unattended-upgrades restart

This is what happened after running that.

root@instance-1:/home/keifer_bly# apt-get install -y unattended-upgrades apt-listchanges
Reading package lists... Done
Building dependency tree
Reading state information... Done
apt-listchanges is already the newest version (3.10).
unattended-upgrades is already the newest version (0.93.1+nmu1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@instance-1:/home/keifer_bly# cp /usr/share/unattended-upgrades/20auto-upgrades
cp: missing destination file operand after '/usr/share/unattended-upgrades/20auto-upgrades'
Try 'cp --help' for more information.

What file would be missing I wonder? Thanks.

--Keifer

On Sat, May 18, 2019 at 6:35 AM <lists@xxxxxxxxxxxxxxx> wrote:
On 17.05.2019 02:22, Neel Chauhan wrote:

> But I'd advise just giving up on cron. For automatic updates, you
> should look into unattended-upgrades instead of using cron.
+1

on Debian:

apt-get install -y unattended-upgrades apt-listchanges
cp /usr/share/unattended-upgrades/20auto-upgrades
/etc/apt/apt.conf.d/20auto-upgrades
service unattended-upgrades restart

Default it upgrades the security sources.
see comments in 50unattended-upgrades

--
Ciao Marco!
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays