Skip to content

Adjust the punctuation marks #2735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 16, 2025
Merged

Adjust the punctuation marks #2735

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2b79614
Adjust the punctuation marks
jimcat8 Jun 8, 2025
826df8f
update
jimcat8 Jun 8, 2025
96ca8a1
Revise the wording of the explanatory text
jimcat8 Jun 8, 2025
9981fca
Update time
jimcat8 Jun 8, 2025
edd247f
Modify pronouns based on the context
jimcat8 Jun 8, 2025
9ac2b46
Readjust the layout of text content
jimcat8 Jun 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 17 additions & 17 deletions docs/books/admin_guide/11-tasks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ If the same user exists in `/etc/cron.deny` and `/etc/cron.allow` at the same ti

When a user schedules a task, there is a file created with their name under `/var/spool/cron/`.

This file contains all the information the `crond` needs to know regarding tasks created by this user, including the commands or programs to run, and the schedule for running them (hour, minute, day, etc.). Note that the minimum time unit that `crond` can recognize is 1 minute. There are similar scheduling tasks in RDBMS (such as MySQL), where time-based scheduling tasks are referred to as the "Event Scheduler." The minimum time unit it can recognize is 1 second, and event-based scheduling tasks are referred to as "Triggers."
This file contains all the information the `crond` needs to know regarding tasks created by this user, including the commands or programs to run, and the schedule for running them (hour, minute, day, etc.). Note that the minimum time unit that `crond` can recognize is 1 minute. There are similar scheduling tasks in RDBMS (such as MySQL), where time-based scheduling tasks are referred to as the "Event Scheduler" (whose recognizable time unit is 1 second), and event-based scheduling tasks are referred to as "Triggers".

![Cron tree](images/tasks-001.png)

Expand All @@ -147,14 +147,14 @@ Example:
|--------|-----------------------------------------------------------|
| `-e` | Edits the schedule file with vi |
| `-l` | Displays the contents of the schedule file |
| `-u` | Sets the name of the user whose schedule file is to be manipulated |
| `-u <user>` | Specify a single user to operate |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is good.

| `-r` | Deletes the schedule file |

!!! Warning

`crontab` without options deletes the old schedule file and waits for the user to enter new lines. You have to press <kbd>ctrl</kbd> + <kbd>d</kbd> to exit this editing mode.

Only the `root` can use the `-u user` option to manage another user's schedule file.
Only the `root` can use the `-u <user>` option to manage another user's schedule file.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also fine with this change.

The example above allows the root to schedule a task for user1.

Expand Down Expand Up @@ -206,12 +206,12 @@ The `crontab` file is structured according to the following rules.

To simplify the notation for the definition of time, it is advisable to use special symbols.

| Wildcards | Description |
| Special symbol | Description |
|---------------|----------------------------------|
| `*` | Indicates all possible values of the field |
| `-` | Indicates a range of values |
| `,` | Indicates a list of values |
| `/` | Defines a step |
| `*` | Indicates all the time values of the field |
| `-` | Indicates a continuous time range |
| `,` | Indicates the discontinuous time range |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you mean "Indicates a non-contiguous time range" rather than "discontinuous"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you mean "Indicates a non-contiguous time range" rather than "discontinuous"

It seems that native speakers may also confuse the usage of these two words

| `/` | Indicateds time interval |

Examples:

Expand All @@ -221,19 +221,19 @@ Script executed on April 15 at 10:25 am:
25 10 15 04 * /root/scripts/script > /log/…
```

Run at 11 am and then at 4 pm every day:
Run the task once a day at 11 am and once a day at 4 pm:

```bash
00 11,16 * * * /root/scripts/script > /log/…
```

Run every hour from 11 am to 4 pm every day:
The task runs once an hour from 11 am to 4 pm every day:

```bash
00 11-16 * * * /root/scripts/script > /log/…
```

Run every 10 minutes during working hours:
Run every 10 minutes during working hours on weekdays:

```bash
*/10 8-17 * * 1-5 /root/scripts/script > /log/…
Expand All @@ -254,12 +254,12 @@ For the root user, `crontab` also has some special time settings:

A user, rockstar, wants to edit his `crontab` file:

1. `crond` checks to see if he is allowed (`/etc/cron.allow` and `/etc/cron.deny`).
1. The `crond` daemon checks to see if the user is allowed (`/etc/cron.allow` and `/etc/cron.deny`).

2. If he is, he accesses his `crontab` file (`/var/spool/cron/rockstar`).
2. If the user is allowed, they access their `crontab` file (`/var/spool/cron/rockstar`).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then this would be: "2. If the user is allowed, they access their crontab file (/var/spool/cron/rockstar).

Every minute `crond` reads the schedule files.
The `crond` daemon:

3. It executes the scheduled tasks.

4. It reports systematically in a log file (`/var/log/cron`).
* Reads - Reads the scheduled task files of all users every minute.
* Runs - Runs tasks according to the schedule.
* Writes - Writes the corresponding events and messages to the (`/var/log/cron`) file.