KERNEL="IBMtape*", NAME="%k", OWNER="tsminst1", GROUP="tsmsrvrs" KERNEL="IBMchanger*", NAME="%k", OWNER="tsminst1", GROUP="tsmsrvrs" KERNEL="IBMtape*n", NAME="%k", MODE="0666"įor example, create the following file to modify the library and drive devices owner to tsminst1 and group to tsmsrvrs : When the lin_taped daemon is not installed, you must create a udev rule to assign device permissions that remain consistent across reboot.įor example, create the following file to modify the library and drive devices permissions to 666 : Despite manually changing the device permissions with the chmod commands, the device permissions are reset on reboot. In this case, the lin_taped daemon was not installed and no udev rule was configured. When the lin_taped daemon is not installed and no udev rule is configured, the library and tape devices are configured with root owership and permissions set to 600. When the lin_taped daemon is installed, the library and tape devices are configured with root owership and permissions are set to 666.
Subsequently, the Tivoli Storage Manager instance fails to access the library and drives and the following error is logged in the activity log :ĪNR8840E Unable to open device /dev/IBMchanger0 with file handle 13 and PVRRC 153. The Linux machine is then rebooted and the devices permissions are automatically changed as follows :Ĭrw- 1 root root 251, 2048 Feb 6 11:26 /dev/IBMchanger0Ĭrw- 1 root root 251, 0 Feb 6 11:26 /dev/IBMtape0Ĭrw- 1 root root 251, 1 Feb 6 11:26 /dev/IBMtape1 The following commands are used to change the permissions :Īfter the commands are run, the devices have the following permissions :Ĭrw-rw-rw- 1 root root 251, 2048 Feb 6 10:53 /dev/IBMchanger0Ĭrw-rw-rw- 1 root root 251, 0 Feb 6 10:53 /dev/IBMtape0Ĭrw-rw-rw- 1 root root 251, 1 Feb 6 10:53 /dev/IBMtape1 The library and tape drive devices permissions are then changed with the chmod commands so that server instance userid has access to the devices.
0 kommentar(er)
