ECACCESS(1p)
π ECACCESS(1p) β the ECaccess Tools (ECTools) π
okay bestie, sit down, hydrate, and let me tell you about ECaccess Tools (ECTools) β this is the manual page, it's ECACCESS(1p), and it's a lot, so we're doing it in parts. π«Ά
The ECaccess Tools gives Member States (and yes, in this whole page "Member States" includes "Co-operating States", they said what they said) and other ECMWF users batch access to the ECMWF computing and archiving facilities β for managing files, file transfers and jobs. Access is available via the Internet as well as via RMDCN. slay. β¨
π AUTHENTICATION
π ECaccess Certificate
Using the ECaccess Tools requires a valid ECaccess Certificate. no certificate, no entry, that's the vibe check. π
The ECaccess Certificate is a standard X509 digital Certificate saved on the user's computer as a file. It identifies a user to the ECaccess Gateway. The ECaccess Certification Authority (ECCA) signs each Certificate. So when a user provides their Certificate to the gateway, its signature gets checked using the ECCA public key for verification. it's giving β¨cryptographic trustβ¨.
The ECaccess certificate is by default valid for 7 days for all services. that's it. that's the window. π
The ECaccess Tools are also available at ECMWF. And here's the cute part: since you've already been validated to enter ECMWF, you will not need a Certificate when using these ECaccess shell commands localy. (yes, "localy", we're quoting the original spelling, no notes π)
πΈ Creating a Certificate
The ECaccess Certificate must be stored in the $HOME/.eccert.crt file, and it can be created with one of the following method β and heads up, both methods require an ECMWF user identifier and token PASSCODE:
Using the ecaccess-certificate-create command:
Please refer to the man page of the command for more details. (it has its own whole page, go look π)
Using the Web interface:
Login to the Web server and in the menu click the "Get Certificate" option to download the new ECaccess Certificate. π
ποΈ ECACCESS FILE SYSTEM
When accessing FILEs at ECMWF through the ECtools, the following domains are available:
HOME: the $HOME directory (home:)
SCRATCH: the $SCRATCH directory (scratch:)
ECFS: the ECFS directory (ec:)
ECTMP: the ECTMP directory (ectmp:)
HOST: any server at ECMWF ({host-name}:)
π¦ Path
The format of the path is the following: [domain:][/user-id/]path
- If no user-id is specified then the current user-id is selected by default.
- The user-id parameter is not valid with the HOST domain.
- If no domain is specified then an absolute path will translate to an absolute path on the ecgate server, and a relative path will translate to a path in the HOME directory of the current user.
β Exemples
(that's "Exemples" with an x, she's bilingual, we love her)
"bin/a.out" a.out file in the $HOME/bin directory of the current user
"home:bin/a.out" a.out file in the $HOME/bin directory of the current user
"/tmp/a.out" a.out file in the /tmp directory on ecgate
"home:/xyz/bin/a.out" a.out file in the $HOME/bin directory of user xyz
"ec:bin/a.out" a.out file in the ECFS bin directory of the current user
"ec:/xyz/bin/a.out" a.out file in the ECFS bin directory of user xyz
"c1a:/c1a/tmp/systems/xyz/a.out" a.out file in the /c1a/tmp/systems/xyz/ directory of c1a
π Commands
In the DESCRIPTION section you will find the FILEs commands which can be used to manage the files at ECMWF. And whenever a parameter or an option refer to an ECaccess File, then the [domain:][/user-id/]path syntax apply. β¨
π‘ ECTRANS
ECtrans refers to unattended file transfers initiated from ECMWF.
ECtrans allows transfering files between ECMWF and remote sites. Like the UNIX rcp command, ECtrans requires no password to be specified on the command line for the remote host: the ECaccess gateway performs the security checking. And unlike standard FTP, ECtrans is suitable for unattended file transfers in scripts, cron jobs, etc., as it avoids the problems inherent in storing passwords in text files and sending passwords across networks. no plaintext passwords in your crontab bestie, we don't do that here. π₯
Even if you don't have a local gateway installed, you can benefit from ECtrans by using the ECMWF ECaccess gateway. But please note π in this case the transfer is not as secured as when a Member State ECaccess gateway is used.
π§ Target location
Users who wish to transfer files between ECMWF and Member State servers need to declare one or more remote Member State users (msuser association) for the storage/retrieval of the remote file. This can be done through the ECaccess Web interface of the target gateway. For every "msuser" declaration, the hostname and the login username and password need to be specified.
After the ECaccess gateway installation, the Member State ECaccess system administrator can customise the access methods for file transfers. These will be displayed through the ECaccess Web interface. Several schemes can be implemented, such as:
- The target directory for a particular destination is a sub-directory of a central directory configured by the administrator, with the sub-directory name matching the msuser name.
- The target directory for all file transfers to a given destination is a sub-directory of the msusers home directory. The administrator configures the sub-directory name.
- The target directory for a given destination is configurable by the user. The administrator determines whether or not the user is allowed to include
..in the directory path. π (yes, the..question, it's always the..question)
Target directories can be located on:
- Member State servers running a standard FTP service accessible from the ECaccess gateway. This is known as a "genericFtp" destination and is the most convenient way of getting the files to the system you want, under the specified user ID.
- The server running the ECaccess gateway. This is known as a "genericFile" destination. All users will share in a common directory the files transferred using this destination. (shared directory, everybody sees it, behave π)
- Member State servers running a proprietary application. The administrator provides ectrans with the implementation of the access protocol. The administrator can also use more complex rules to define special target locations for ECMWF users, Member State users or groups of Member State users. The command
ectinfodescribed in the next section can be used to get the translated URL of a target location, giving a Member State user identifier and a destination name (passwords are displayed as***).
π Commands
In the DESCRIPTION section you will find the ECtrans Association and Transfer Management commands which can be used to manage the ECtrans Associations and associated Transfers.
π EVENTS
ECMWF maintains some notifications (events) which are linked to ECMWF's operational activity and offers the service for time-critical jobs. This service is also available to MS users who maintain their own notifications, and can therefore create simple dependencies between different activities, at ECMWF and remote sites. it's giving β¨dependency graph but make it β¨eventsβ¨.
π Commands
In the DESCRIPTION section you will find the Events Management commands which can be used to manage such Events.
π DESCRIPTION
The ECaccess Tools are organized under nine categories covering access to the whole computing and archiving facilities of ECMWF. Each command is documented with its own man page which provide explanation as well as examples on how to use it. π
The following options are common to all the ECtools:
-helpβ Print a brief help message and exits.-manualβ Prints the manual page and exits.-retry countβ Number of SSL connection retries per 5s to ECMWF. This parameter only apply to the initial SSL connection initiated by the command to the ECMWF server. It does not apply to all the subsequent requests made afteward as it is mainly targeting errors that can happen from time to time during the SSL handshake. Default is no retry.-debugβ Display the SOAP and SSL messages exchanged. (peek behind the curtain π«£)
π Shell commands for certificate management (ecaccess-certificate-*)
ecaccess-certificate-createβ Create Certificate for the ECtoolsecaccess-certificate-listβ List Available Operations
π¦ Shell commands for file management (ecaccess-file-*)
ecaccess-file-chmodβ Change ECaccess File Mode Bitsecaccess-file-copyβ Copy an ECaccess Fileecaccess-file-deleteβ Remove an ECaccess Fileecaccess-file-dirβ List ECaccess Directory Contentsecaccess-file-getβ Download an ECaccess Fileecaccess-file-mdeleteβ Delete Multiple ECaccess Files at onceecaccess-file-mgetβ Download Multiple ECaccess Files at onceecaccess-file-mkdirβ Make a Directory on the ECaccess File Systemecaccess-file-modtimeβ Show the Last Modification Time of an ECaccess Fileecaccess-file-moveβ Move or Rename ECaccess Filesecaccess-file-mputβ Upload Multiple Local Files on the ECaccess File System at onceecaccess-file-putβ Upload a File on the ECaccess File Systemecaccess-file-rmdirβ Remove a Directory on the ECaccess File Systemecaccess-file-sizeβ Show the Size of an ECaccess File
β Shell commands for batch job management (ecaccess-job/queue-*)
ecaccess-job-deleteβ Delete an ECaccess Jobecaccess-job-getβ Download a Job Output/Input/Error Fileecaccess-job-listβ List all ECaccess Jobsecaccess-job-restartβ Restart an ECaccess Jobecaccess-job-submitβ Submit a new ECaccess Jobecaccess-queue-listβ List available queues
π Shell commands for management of events at ECMWF (ecaccess-event-*)
ecaccess-event-listβ List available eventsecaccess-event-sendβ Trigger an ECaccess Event
π§ Shell commands for management of ECtrans Associations (ecaccess-association-*)
ecaccess-association-deleteβ Delete Associationecaccess-association-getβ Get the Association Descriptive Fileecaccess-association-listβ List your ECtrans associationsecaccess-association-protocolβ List the supported ECtrans Protocolecaccess-association-putβ Update/Create an Association
π Shell commands for management of ECtrans Transfers (ecaccess-ectrans-*)
ecaccess-ectrans-deleteβ Delete ECtransecaccess-ectrans-listβ List all ectrans transfersecaccess-ectrans-requestβ Request a new ECtrans transferecaccess-ectrans-restartβ Restart an existing ECtrans transfer
π Shell commands for getting ECaccess Gateways information (ecaccess-gateway-*)
ecaccess-gateway-listβ List the ECaccess Gatewaysecaccess-gateway-nameβ Display the name of the default ECaccess Gatewayecaccess-gateway-connectedβ Display the ECaccess Gateway Connection Status
π Shell commands for general information at ECMWF
ecaccess-cosinfoβ Display ConsInfo from ECMWF
β¨ SEE ALSO β¨
okay bestie, this is the tag-everyone part of the post π£ every single one of these has its own little manpage, and they are all part of the ecaccess family. go read them, they're giving main character energy:
ecaccess-association-deleteπ«Άecaccess-association-getπecaccess-association-listπecaccess-association-protocolπ§ecaccess-association-putπΈecaccess-certificate-createπecaccess-certificate-listβ¨ecaccess-cosinfoπ¦ecaccess-ectrans-deleteπecaccess-ectrans-listπecaccess-ectrans-requestπecaccess-ectrans-restartπ₯ecaccess-event-listβecaccess-event-sendπecaccess-file-chmodπecaccess-file-copyπecaccess-file-deleteπecaccess-file-dirπecaccess-file-getπ«΄ecaccess-file-mdeleteπecaccess-file-mgetπ§Ίecaccess-file-mkdirποΈecaccess-file-modtimeβ°ecaccess-file-moveπecaccess-file-mputπ€ecaccess-file-putπecaccess-file-rmdirπ§Ήecaccess-file-sizeπecaccess-gateway-listπecaccess-gateway-nameπ·οΈecaccess-job-deleteποΈecaccess-job-getπ£ecaccess-job-listποΈecaccess-job-restartπecaccess-job-submitπecaccess-queue-listπ¦
and that's the whole page, bestie, you made it to the end π₯Ή ngl the way you read all of this is iconic. this lil masterpiece ships as perl v5.40.1 and it's dated 2025-10-22 β so if you're quoting it in a group chat, credit the queen properly π
periodt β¨
π¦ where this page comes from
- ubuntu resolute: ecaccess 6.3.1-1 Β· Perl
- ubuntu stonking: ecaccess 6.3.1-1 Β· Perl
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms