diff --git a/core/smb4kmountsettings_bsd.kcfg b/core/smb4kmountsettings_bsd.kcfg
index b766fa3..d2017f4 100644
--- a/core/smb4kmountsettings_bsd.kcfg
+++ b/core/smb4kmountsettings_bsd.kcfg
@@ -1,284 +1,284 @@
KUserQDirThis is the user ID (a number) that the files and directories of the mounted share will have.falseThis is the user ID (a number) that the files and directories of the mounted share will have.
- QString("%1").arg(KUser(KUser::UseRealUserID).userId().nativeId())
+ KUserId::currentUserId().toString()This is the group ID (a number) that the files and directories of the mounted share will have.falseThis is the group ID (a number) that the files and directories of the mounted share will have.
- QString("%1").arg(KUserGroup(KUser::UseRealUserID).groupId().nativeId())
+ KGroupId::currentGroupId().toString()This is the file mode that will be used for creating files. It must be defined in octal.falseThis is the file mode that will be used for creating files. It must be defined in octal.0755This is the directory mode that will be used for creating directories. It must be defined in octal.falseThis is the directory mode that will be used for creating directories. It must be defined in octal.0755This is the character set that is used by the client side (i.e. your side) for codepage to charset translations. If you keep the default setting, Smb4K will try to automatically determine the charset by looking up the "unix charset" option in the smb.conf.falseThis is the character set that is used by the client side (i.e. your side) for codepage to charset translations. If you keep the default setting, Smb4K will try to automatically determine the charset by looking up the "unix charset" option in the smb.conf.default_charsetThis is the character set that is used by the server. If you keep the default setting, Smb4K will try to automatically determine the codepage by looking up the "dos charset" option in the smb.conf file.default_codepageThis is the prefix where Smb4K will create the mount points and mount the remote shares.QUrl::fromLocalFile(QDir::homePath()+"/smb4k/")All names of the subdirectories created by Smb4K below the mount prefix will be lowercase.falseUnmount all shares that belong to you when the program exits. Shares that are owned by other users are ignored.falseRemount all your shares that were mounted when you exited the program or changed a profile. If the remounting of a share fails, Smb4K will retry the next time it is started. Shares that were mounted by other users are ignored. Please note that this setting does not affect the automatic remounting of shares when your computer woke up from a sleep state.falseSet the number of attempts that are made to remount shares before Smb4K gives up.11001Set the time that elapses between attempts to remount shares.1305Allow the unmounting of shares that were mounted by other users. Please think before you enable this option.falseForce the unmounting of inaccessible shares (Linux only). In case a share is inaccessible, a lazy unmount is performed. Before the actual unmount is performed, a warning dialog is shown asking to approve the unmount.falseYou will not only see the shares that were mounted and are owned by you, but also all other mounts using the SMBFS and CIFS file system that are present on the system.false
diff --git a/core/smb4kmountsettings_linux.kcfg b/core/smb4kmountsettings_linux.kcfg
index 7e046dd..b0c75c4 100644
--- a/core/smb4kmountsettings_linux.kcfg
+++ b/core/smb4kmountsettings_linux.kcfg
@@ -1,334 +1,334 @@
KUserQDirMost versions of Samba support the CIFS Unix or POSIX extensions. For these servers, some options are not needed, because the right values are negotiated during the mount process. For other servers, you might want to uncheck this option, so that predefined values can be passed to the server. Please note that if your computer is located in a Windows dominated network neighborhood with only a few Samba servers, you can safely uncheck this option and define custom options for the Samba servers.falseThis is the user ID (a number) that the files and directories of the mounted share will have. If you are using the CIFS filesystem under Linux and the remote server supports the CIFS Unix Extensions, this setting will be ignored unless the assignment of the user ID is forced.trueThis is the user ID (a number) that the files and directories of the mounted share will have. If you are using the CIFS filesystem under Linux and the remote server supports the CIFS Unix Extensions, this setting will be ignored unless the assignment of the user ID is forced.
- QString("%1").arg(KUser(KUser::UseRealUserID).userId().nativeId())
+ KUserId::currentUserId().toString()This is the group ID (a number) that the files and directories of the mounted share will have. If you are using the CIFS filesystem under Linux and the remote server supports the CIFS Unix Extensions, this setting will be ignored unless the assignment of the group ID is forced.trueThis is the group ID (a number) that the files and directories of the mounted share will have. If you are using the CIFS filesystem under Linux and the remote server supports the CIFS Unix Extensions, this setting will be ignored unless the assignment of the group ID is forced.
- QString("%1").arg(KUserGroup(KUser::UseRealUserID).groupId().nativeId())
+ KGroupId::currentGroupId().toString()This is the file mode that will be used for creating files. It must be defined in octal. In case the CIFS file system is used, this setting only takes effect if the server does not support the CIFS Unix Extensions.trueThis is the filemode that will be used for creating files. It must be defined in octal. In case the CIFS file system is used, this setting only takes effect if the server does not support the CIFS Unix Extensions.0755This is the directory mode that will be used for creating directories. It must be defined in octal. In case the CIFS file system is used, this setting only takes effect if the server does not support the CIFS Unix Extensions.trueThis is the directory mode that will be used for creating directories. It must be defined in octal. In case the CIFS file system is used, this setting only takes effect if the server does not support the CIFS Unix Extensions.0755This is the port that is exclusively used to mount shares from remote servers. The default value is 445 (CIFS file system).falseThis is the port that is exclusively used to mount shares from remote servers. The default value is 445 (CIFS file system).165535445This is the character set that is used by the client side (i.e. your side) either to convert local path names to and from Unicode (CIFS, Linux) or for codepage to charset translations (SMBFS, FreeBSD). If you keep the default setting, Smb4K will try to automatically determine the charset by looking up the "unix charset" option in the smb.conf.falseThis is the character set that is used by the client side (i.e. your side) either to convert local path names to and from Unicode (CIFS, Linux) or for codepage to charset translations (SMBFS, FreeBSD). If you keep the default setting, Smb4K will try to automatically determine the charset by looking up the "unix charset" option in the smb.conf.default_charsetHere you can choose if the shares should be mounted in read-write or read-only mode.falseHere you can choose if the shares should be mounted in read-write or read-only mode.ReadWriteInstruct the client (i.e. your side) to ignore any user ID (UID) provided by the server for files and directories and to always assign the owner to be the value of the transmitted UID.falseInstruct the client (i.e. your side) to ignore any group ID (GID) provided by the server for files and directories and to always assign the owner to be the value of the transmitted GID.falseThe client side (i.e. your side) will check if you have the right UID/GID to manipulate a file or directory. You might want to switch this feature off if the server(s) support the CIFS Unix Extensions and you are not allowed to access the files and directories. This setting does not affect the normal ACL check.trueIn case the server supports the CIFS Unix Extensions, the client side (i.e. your side) attempts to set the effective UID and GID of the current process on newly created files, directories and devices. If this feature is turned off, the server will set the UID and GID to the default for the share. It is recommended that you read the manual page of mount.cifs before you change this setting.falseUse inode numbers (unique persistent file identifiers) returned by the server instead of automatically generating temporary inode numbers on the client side.trueDo not use locking. Do not start lockd.falseTranslate six of the seven reserved characters (including the colon, question mark, pipe, asterisk, greater than and less than characters but not the backslash) to remap range (above 0xF000). This allows you to open files that were created with such characters. This has no effect if the server does not support Unicode.falseDefine which version of the SMB protocol is to be used.falseDefine which version of the SMB protocol is to be used.ThreePointZeroDefine how read and write requests are handled. In case you choose to not cache file data at all, the client never utilizes the cache for normal reads and writes. It always accesses the server directly to satisfy a read or write request. If you choose to follow the CIFS/SMB2 protocol strictly, the cache is only trusted if the client holds an oplock. If the client does not hold an oplock, then the client bypasses the cache and accesses the server directly to satisfy a read or write request. Choosing to allow loose caching semantics can sometimes provide better performance on the expense of cache coherency. This option might cause data corruption, if several clients access the same set of files on the server at the same time. Because of this, the strict cache mode is recommended.falseDefine how read and write requests are handled. In case you choose to not cache file data at all, the client never utilizes the cache for normal reads and writes. It always accesses the server directly to satisfy a read or write request. If you choose to follow the CIFS/SMB2 protocol strictly, the cache is only trusted if the client holds an oplock. If the client does not hold an oplock, then the client bypasses the cache and accesses the server directly to satisfy a read or write request. Choosing to allow loose caching semantics can sometimes provide better performance on the expense of cache coherency. This option might cause data corruption, if several clients access the same set of files on the server at the same time. Because of this, the strict cache mode is recommended.StrictSecurity mode for mount.cifs. To be able to use this mode, the CIFS kernel module 1.40 or later is required.falseSecurity mode for mount.cifs. To be able to use this mode, the CIFS kernel module 1.40 or later is required.NtlmsspHere you can enter advanced options for the CIFS file system in a comma-separated list (refer to the manual page of mount.cifs to learn more). The list will be added AS IS to the "-o" argument of mount.cifs. Please do not enter options that have already been defined in the configuration dialog.This is the prefix where Smb4K will create the mount points and mount the remote shares.QUrl::fromLocalFile(QDir::homePath()+"/smb4k/")All names of the subdirectories created by Smb4K below the mount prefix will be lowercase.falseUnmount all shares that belong to you when the program exits. Shares that are owned by other users are ignored.falseRemount all your shares that were mounted when you exited the program or changed a profile. If the remounting of a share fails, Smb4K will retry the next time it is started. Shares that were mounted by other users are ignored. Please note that this setting does not affect the automatic remounting of shares when your computer woke up from a sleep state.falseSet the number of attempts that are made to remount shares before Smb4K gives up.11001Set the time that elapses between attempts to remount shares.1305Allow the unmounting of shares that were mounted by other users. Please think before you enable this option.falseForce the unmounting of inaccessible shares (Linux only). In case a share is inaccessible, a lazy unmount is performed. Before the actual unmount is performed, a warning dialog is shown asking to approve the unmount.falseYou will not only see the shares that were mounted and are owned by you, but also all other mounts using the SMBFS and CIFS file system that are present on the system.false