[Savannah-cvs] [560] update info on cron

[ineiev]

Revision: 560
          
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=560
Author:   ineiev
Date:     2023-02-09 03:21:51 -0500 (Thu, 09 Feb 2023)
Log Message:
-----------
update info on cron

Modified Paths:
--------------
    trunk/sviki/SshAccess.mdwn

Modified: trunk/sviki/SshAccess.mdwn
===================================================================
--- trunk/sviki/SshAccess.mdwn  2023-02-09 08:20:59 UTC (rev 559)
+++ trunk/sviki/SshAccess.mdwn  2023-02-09 08:21:51 UTC (rev 560)
@@ -1,4 +1,4 @@
-ssh and savannah
+SSH and Savannah
 ================
 
 OpenSSH 8.8 SHA-1 Deprecation October 2021
@@ -74,14 +74,10 @@
 Debugging
 ---------
 
-If you just registered your ssh key a few minutes ago, please wait for
-an hour and try again.  Many tasks are implemented by hourly cron jobs
-that scan for queued tasks every hour.
-
 GPG keys are not used for Savannah operations.  We suggest you upload
 a GPG key because it is used by the FSF for file uploads elsewhere.
 But for version control repository access you have to create and
-register an ssh key.
+register an SSH key.
 
 SSH access is allowed for registered members who are a member of at
 least one project.  If you are not a member of any project then you
@@ -145,8 +141,6 @@
 connect to Savannah from different computers.  You can delete them when
 you do not use that key pair anymore.
 
-Wait for the next cron job (worst case: 1 hour).
-
 Q: RSA or DSA?
 --------------
 We recommend against using DSA keys.  We recommend using ED25519
@@ -253,8 +247,7 @@
 
 -   If, when (for example) you try to use cvs, you're rejected with
     `Permission denied`, that means that your key is not
-    recognized. It could be a matter of time (cron job) or, generally,
-    it means that your key is not a correct ssh2 key (the key
+    recognized. Generally, it means that your key is not a correct ssh2 key 
(the key
     registration page contains a sample key for you to compare). If you
     think you have done everything correctly, use the support manager
     (<https://savannah.gnu.org/support/?group=administration>)
@@ -417,7 +410,7 @@
     is well GNU Savannah, and not a fake website. It is totally
     different from your SSH key.
 
--   What about `authorized_keys`? `authorized_keys` is maintained on the
+-   **Obsolete**: What about `authorized_keys`? `authorized_keys` is 
maintained on the
     server side, at Savannah. This is done automatically, based on the
     public keys you upload to the web interface. (Savannah admin info:
     specifically, in `/etc/ssh/authorized_keys/`USERNAME on the