the result of "setfacl --modify" will get reverted after a reboot

 The `setfacl` command is used to set file access control lists (ACLs) on a file or directory. If you're finding that the changes made with `setfacl --modify` are not persistent after a reboot, it might be due to the default ACL settings or the file system type you're using.


Here are a few considerations:


1. **File System Type**: Not all file systems support ACLs, and support for ACLs can vary between different filesystems. Ensure that you're using a filesystem that supports ACLs, like ext4 or XFS on Linux.


2. **Default ACLs**: Some filesystems, like ext4, support default ACLs. These default ACLs can be applied to newly created files and directories. If you're setting ACLs on a directory, make sure you're also setting any necessary default ACLs if you want them to be applied to new files and directories created within that directory.


3. **Boot Scripts or Configuration**: Some operating systems or distributions have scripts or configuration files that reset file permissions or ACLs during boot. You might want to check if there are any scripts or configurations that interfere with your ACL settings.


4. **Permissions and Inheritance**: Be aware of how ACLs interact with regular Unix permissions. ACLs can be more complex, and the effective permissions are often the result of both the ACLs and the standard file permissions. Make sure you're setting ACLs in a way that aligns with your desired access control.


5. **Documentation**: Check your system's documentation for ACLs and boot-time behavior specific to your distribution.


If you can provide more specific details about your setup and the issue you're facing, I can offer more targeted assistance.

Comments

Post a Comment

Popular posts from this blog

bad character U+002D '-' in my helm template

 In Helm templates, the hyphen character (`-`) can sometimes be treated as a reserved character, particularly when defining values or labels. To include a hyphen character in a Helm template without issues, you can use one of the following approaches: 1. **Quoting the Hyphen:**    You can enclose the hyphen in double quotes, like this:    ```yaml    key: "-"    ```    This way, Helm will interpret the hyphen as a string rather than an operator. 2. **Using Backticks:**    If you need to use the hyphen within a Go template function or inside backticks, you can escape it with a backslash (`\`), like this:    ```yaml    value: `{{ .Values.someField | printf "%s \\-" }}`    ```    The backslash prevents Helm from interpreting the hyphen as a special character. 3. **Variable Assignment:**    Assign the value to a variable and use it. For example:    ```yaml    {{- $hyphen := "-" }}    key: {{ $hyphen }}    ```    This way, you can use the variable `$hyphen` wher
Read more

GitLab pipeline stopped working with invalid yaml error

 When your GitLab pipeline has stopped working with an "invalid YAML" error, it means there's a problem with your `.gitlab-ci.yml` file. This could be due to syntax errors, incorrect indentation, or other issues in your pipeline configuration. Here's how to troubleshoot and resolve this issue: 1. **Check for Syntax Errors**:    Carefully review your `.gitlab-ci.yml` file for any syntax errors. Common issues include missing colons, indentation problems, or mismatched quotation marks. Use a YAML linter or an online YAML validator to identify and correct syntax errors. 2. **Indentation**:    YAML relies heavily on proper indentation. Make sure that all lines within the same block have consistent indentation (typically using spaces, not tabs). Incorrect indentation can cause YAML parsing errors. 3. **Dashes and Lists**:    Ensure that you use the correct syntax for lists (arrays) in YAML by starting each item with a dash (`-`). Be consistent with your use of dashes throug
Read more

How do I add a printer in OpenSUSE which is being shared by a CUPS print server?

 To add a printer in openSUSE that is being shared by a CUPS print server, you can use the following steps: 1. **Ensure CUPS Client is Installed:**    Make sure your openSUSE system has the CUPS client tools installed. You can install them using the following command:    ```bash    sudo zypper install cups-client    ``` 2. **Discover Available Printers:**    Use the `lpinfo` command to discover available printers on your CUPS print server. Replace `cups-server-hostname` with the hostname or IP address of your CUPS server:    ```bash    lpinfo -v -h cups-server-hostname:631    ```    This command should list the printers shared by the CUPS server. 3. **Add a Printer:**    Use the `lpadmin` command to add a printer. Replace `printer-name` with the name of the printer you want to add and `printer-uri` with the URI obtained from the `lpinfo` command:    ```bash    sudo lpadmin -p printer-name -E -v printer-uri    ```    For example:    ```bash    sudo lpadmin -p MyPrinter -E -v socket://cu
Read more