[vaggie_talez]

Just keep in mind, whether it successfully works or not, it's going to print the success message. It has no kind of error control (which for your implementation is probably fine, this is changing file permissions, not rocket science, lol)

If you do decide to run it as a cron, you should probably use absolute paths instead of relative (including the commands), since I've had a number of scripts run fine when executed by a user, but break when trying it as a cron job. Adding the ab paths fixed it. Also, I agree with the sentiment that a cron job ever couple minutes for something like this probably isn't a great idea.

[Loki123]

chmod 775 /$FOLDER/*
means that just the permissions on files and directories inside $FOLDER get changed. Thus $FOLDER/file but not $FOLDER/folder/file ...

@OP
your script looks fine. There are probably better ways to do this but it will work adding it to cron.
/path/to/script

Yes, is allowed thus it being run all the time.

Cron explanation if you don't know how.

# * command to execute
# ┬ ┬ ┬ ┬ ┬
# │ │ │ │ │
# │ │ │ │ │
# │ │ │ │ └───── day of week (0 - 7) (0 to 6 are Sunday to Saturday, or use names; 7 is Sunday, the same as 0)
# │ │ │ └────────── month (1 - 12)
# │ │ └─────────────── day of month (1 - 31)
# │ └──────────────────── hour (0 - 23)
# └───────────────────────── min (0 - 59)

[Loki123]

My mistake, forgot the option.

He would need to put -R behind chmod.

so the command would look like this:

Code

chmod -R /$folder

-R =

The -R flag was there aldready 🤫