Luca Moscato's questions

We have (more than) a linux server on AWS that use a network file system, in our case AWS EFS, mounted on /logs directory.

It happens sometimes that:

• the machine is rebooted
• for any reason the network file system is not mounted, so all process starts to log in /logs but on the main (system) partition
• disk space quickly starts to be low and, in worst case, the disk become completely full.

While debugging the issue a reboot happened and network file system comes back to normal so that my server can mount the disk and starts logging in the correct partition.

BUT the logs generated while network file system are still on the main partition, they are NOT accessible since a disk is mounted in the same /logs directory and they use disk space that cannot be reclaimed.

Is there any way apart unmount the network file system to access that logs so that I can trash or move them to the correct location avoiding to use precious space in system partition?

I have a centos 7 file server and user that can work on shared directory are in group users. With default umask a user is able to create file with the following permissions:

[luca@myserver mydirectory]$ ls -l testfile -rw-rw-r-- 1 luca users 0 18 giu 13.03 testfile.txt

but when an other user, part of the same group users, try to change permissions on the same file I have

[nick@myserver mydirectory]$ chmod a+x testfile.txt chmod: cambio dei permessi di "testfile.txt": Operazione non permessa (change permissions: operation not permitted, sorry for italian)

Why an other user in the same group cannot change file permission for a file that have write permission for user in the same group?

As most company we have different pre-production environment: development, integration, staging, production. We would like to keep these env OS updated but we would like to perform yum update in development, after a couple of days update the exact list of package that has been updated on integration env, after a couple of days in staging, and finally in production. The purpose is to avoid that a new update will pop up during the process and have it running in production at first. As far as I googled, there is no something like 'yum update at this timestamp' Do you know if there is some way to handle this? Asking since we have to deal with mission critical environment. Thx