fedora-docs-l10n/fedora-system-administrat/f31/pages/monitoring-and-automation/Automating_System_Tasks — Spanish @ Fedora Weblate: For more information on how to install new packages in …

Translation

Source change

English type: Plain text

Spanish

Needs editing

Skip

	English	Spanish	Actions
	Black and White Listing of Cron Jobs
	Black and white listing of jobs is used to define parts of a job that do not need to be executed. This is useful when calling the [application]run-parts script on a Cron directory, such as `/etc/cron.daily/`: if the user adds programs located in the directory to the job black list, the [application]run-parts script will not execute these programs.
	To define a black list, create a `jobs.deny` file in the directory that [command]#run-parts# scripts will be executing from. For example, if you need to omit a particular program from `/etc/cron.daily/`, create the `/etc/cron.daily/jobs.deny` file. In this file, specify the names of the programs to be omitted from execution (only programs located in the same directory can be enlisted). If a job runs a command which runs the programs from the `/etc/cron.daily/` directory, such as [command]#run-parts /etc/cron.daily#, the programs defined in the `jobs.deny` file will not be executed.
	To define a white list, create a `jobs.allow` file.
	The principles of `jobs.deny` and `jobs.allow` are the same as those of `cron.deny` and `cron.allow` described in section xref:Automating_System_Tasks.adoc#s2-autotasks-cron-access[Controlling Access to Cron].
	At and Batch
	indexterm:[at]indexterm:[batch] While Cron is used to schedule recurring tasks, the [application]At utility is used to schedule a one-time task at a specific time and the [application]Batch utility is used to schedule a one-time task to be executed when the system load average drops below 0.8.
	Installing At and Batch
	To determine if the [package]at package is already installed on your system, issue the following command:
	[command]#rpm -q at#
	The command returns the full name of the [package]at package if already installed or notifies you that the package is not available.
	To install the packages, use the [command]#dnf# command in the following form as `root`:
	[command]#dnf install _package_pass:attributes[{blank}]#	[command]#dnf install _package_pass:attributes[{blank}]#
	For example, to install both At and Batch, type the following at a shell prompt:
	~]#{nbsp}dnf install at
	For more information on how to install new packages in {MAJOROS}, see xref:package-management/DNF.adoc#sec-Installing[Installing Packages].	Para más información sobre como instalar nuevos paquetes en la instalación de paquetes en {MAJOROS}, vea xref:package-management/DNF.adoc#sec-Installing[Instalando Paquetes].
	Running the At Service
	The At and Batch jobs are both picked by the `atd` service. This section provides information on how to start, stop, and restart the `atd` service, and shows how to configure it to start automatically at boot time.
	Starting and Stopping the At Service
	To determine if the service is running, use the following command:	Para determinar si el servicio está corriendo, use el siguiente comando:
	[command]#systemctl status atd.service#
	To run the `atd` service in the current session, type the following at a shell prompt as `root`:
	[command]#systemctl start atd.service#
	To configure the service to start automatically at boot time, use the following command as `root`:	Para determinar si el servicio está corriendo, use el siguiente comando:
	[command]#systemctl enable atd.service#
	It is recommended that you configure your system to start the `atd` service automatically at boot time.
	Stopping the At Service
	To stop the `atd` service, type the following at a shell prompt as `root`:
	[command]#systemctl stop atd.service#
	To prevent the service from starting automatically at boot time, use the following command as `root`:	Para determinar si el servicio está corriendo, use el siguiente comando:
	[command]#systemctl disable atd.service#