{"schema_version":1,"metadata":{"branch":"release","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:02.361425+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/7.9/packages/amd64/sqlports-7.54.tgz","source_sha256":"2de00144847bf9da3a365be982f101dbb55d591ed7a915ea94984a16ab0e0404","package_count":12059,"source_kind":"sqlports"},"package":{"name":"safecat-1.13p0","path":"sysutils/safecat","url":"/packages/release/sysutils/safecat/","comment":"copy stdin to a qmail-style maildir","homepage":"http://jeenyus.net/linux/software/safecat.html","maintainer":"Armin Wolfermann <armin@wolfermann.org>","description":"safecat is a program which implements D. J. Bernstein's maildir\nalgorithm to copy stdin safely to a file in a specified directory.  With\nsafecat, the user is offered two assurances.  First, if safecat returns\na successful exit status, then all data is guaranteed to be saved in the\ndestination directory.  Second, if a file exists in the destination\ndirectory, placed there by safecat, then the file is guaranteed to be\ncomplete.\n\nWhen saving data with safecat, the user specifies a destination\ndirectory, but not a file name.  The file name is selected by safecat to\nensure that no filename collisions occur, even if many safecat processes\nand other programs implementing the maildir algorithm are writing to the\ndirectory simultaneously.  If particular filenames are desired, then the\nuser should rename the file after safecat completes.  In general, when\nspooling data with safecat, a single, separate process should handle\nnaming, collecting, and deleting these files.  Examples of such a\nprocess are daemons, cron jobs, and mail readers.\n","package_architecture":"amd64","stem":"safecat","readme":null,"dependencies":[],"reverse_dependencies":{"count":0,"url":null},"categories":["sysutils"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}