From 69cac65817d949cda2672ec4f0aa73d5e66a0ba1 Mon Sep 17 00:00:00 2001 From: tpearson Date: Wed, 22 Jun 2011 00:30:31 +0000 Subject: TQt4 port kdenetwork This enables compilation under both Qt3 and Qt4 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdenetwork@1237912 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- filesharing/advanced/nfs/hostprops.ui | 76 +++++++++++++++++------------------ 1 file changed, 38 insertions(+), 38 deletions(-) (limited to 'filesharing/advanced/nfs/hostprops.ui') diff --git a/filesharing/advanced/nfs/hostprops.ui b/filesharing/advanced/nfs/hostprops.ui index 4ff97e28..52a23e14 100644 --- a/filesharing/advanced/nfs/hostprops.ui +++ b/filesharing/advanced/nfs/hostprops.ui @@ -1,6 +1,6 @@ HostProps - + HostProps @@ -22,7 +22,7 @@ 6 - + propertiesGrp @@ -34,7 +34,7 @@ 0 - + 180 0 @@ -59,7 +59,7 @@ 6 - + TextLabel1 @@ -70,7 +70,7 @@ nameEdit - + nameEdit @@ -103,11 +103,11 @@ The host may be specified in a number of ways: <i>IP networks</i> <p> - You can also export directories to all hosts on an IP (sub-) network simultaneously. This is done by specifying an IP address and netmask pair as address/netmask where the netmask can be specified in dotted-decimal format, or as a contiguous mask length (for example, either `/255.255.252.0' or `/22' appended to the network base address result in identical subnetworks with 10 bits of host). + You can also export directories to all hosts on an IP (sub-) network simultaneously. This is done by specifying an IP address and nettqmask pair as address/nettqmask where the nettqmask can be specified in dotted-decimal format, or as a contiguous tqmask length (for example, either `/255.255.252.0' or `/22' appended to the network base address result in identical subnetworks with 10 bits of host). </p> - + publicChk @@ -124,7 +124,7 @@ This is just the same as if you would enter a wildcard in the address field. - + GroupBox7 @@ -149,7 +149,7 @@ This is just the same as if you would enter a wildcard in the address field. 6 - + readOnlyChk @@ -166,7 +166,7 @@ The default is to disallow any request which changes the filesystem </p> - + secureChk @@ -183,7 +183,7 @@ If unsure leave it unchecked. </p> - + syncChk @@ -200,7 +200,7 @@ The default is to allow the server to write the data out whenever it is ready. </p> - + wdelayChk @@ -216,7 +216,7 @@ The default is to allow the server to write the data out whenever it is ready. This option only has effect if sync is also set. The NFS server will normally delay committing a write request to disk slightly if it suspects that another related write request may be in progress or may arrive soon. This allows multiple write requests to be committed to disk with the one operation which can improve performance. If an NFS server received mainly small unrelated requests, this behavior could actually reduce performance, so no wdelay is available to turn it off. </p> - + hideChk @@ -226,13 +226,13 @@ This option only has effect if sync is also set. The NFS server will normally de <b>No hide</b> <p> -This option is based on the option of the same name provided in IRIX NFS. Normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. If it just mounts the parent, it will see an empty directory at the place where the other filesystem is mounted. That filesystem is "hidden". +This option is based on the option of the same name provided in IRIX NFS. Normally, if a server exports two filesystems one of which is mounted on the other, then the client will have to mount both filesystems explicitly to get access to them. If it just mounts the tqparent, it will see an empty directory at the place where the other filesystem is mounted. That filesystem is "hidden". </p> <p> -Setting the nohide option on a filesystem causes it not to be hidden, and an appropriately authorized client will be able to move from the parent to that filesystem without noticing the change. +Setting the nohide option on a filesystem causes it not to be hidden, and an appropriately authorized client will be able to move from the tqparent to that filesystem without noticing the change. </p> <p> -However, some NFS clients do not cope well with this situation as, for instance, it is then possible for two files in the one apparent filesystem to have the same inode number. +However, some NFS clients do not cope well with this situation as, for instance, it is then possible for two files in the one aptqparent filesystem to have the same inode number. </p> <p> The nohide option is currently only effective on single host exports. It does not work reliably with netgroup, subnet, or wildcard exports. @@ -242,7 +242,7 @@ This option can be very useful in some situations, but it should be used with du </p> - + subtreeChk @@ -268,7 +268,7 @@ As a general guide, a home directory filesystem, which is normally exported at t </p> - + secureLocksChk @@ -287,7 +287,7 @@ Early NFS client implementations did not send credentials with lock requests, an - + GroupBox3 @@ -302,7 +302,7 @@ Early NFS client implementations did not send credentials with lock requests, an User Mapping - + AlignAuto @@ -315,7 +315,7 @@ Early NFS client implementations did not send credentials with lock requests, an 6 - + allSquashChk @@ -328,7 +328,7 @@ Early NFS client implementations did not send credentials with lock requests, an Map all uids and gids to the anonymous user. Useful for NFS-exported public FTP directories, news spool directories, etc. </p> - + rootSquashChk @@ -346,15 +346,15 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap </p> - + - layout15 + tqlayout15 unnamed - + TextLabel1_2 @@ -368,7 +368,7 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap <b>Anonym. UID/GID</b> <p> These options explicitly set the uid and gid of the anonymous account. This option is primarily useful for PC/NFS clients, where you might want all requests appear to be from one user. </p> - + anonuidEdit @@ -380,7 +380,7 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap 0 - + 50 0 @@ -392,15 +392,15 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap - + - layout16 + tqlayout16 unnamed - + TextLabel2 @@ -414,7 +414,7 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap <b>Anonym. UID/GID</b> <p> These options explicitly set the uid and gid of the anonymous account. This option is primarily useful for PC/NFS clients, where you might want all requests appear to be from one user. </p> - + anongidEdit @@ -426,7 +426,7 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap 0 - + 50 0 @@ -450,7 +450,7 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap Expanding - + 20 16 @@ -548,11 +548,11 @@ Map requests from uid/gid 0 to the anonymous uid/gid. Note that this does not ap hostprops.ui.h - + modified() - - + + setModified() - - + + -- cgit v1.2.3