October 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Can't access a certain directory over nfs, acl problem.
by Carlos E. R. 26 Oct '15

26 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a directory on a machine, like this (edited for simplicity): cer@AmonLanc:/data/hoard> l total 100 drwxr-xr-x 5 root root 94 Sep 26 2014 ./ drwxr-xr-x 5 root root 4096 Oct 2 20:36 ../ drwxrws---+ 6 john cosas 4096 Nov 1 2014 TheHoard/ - -rw-r--r-- 1 root root 86165 May 24 2014 remote_log cer@AmonLanc:/data/hoard> The entire "/data/hoard/" is an external disk, and I replaced it recently with a much bigger unit (2T). I _think_ it worked before (unsure). You see it has extended attributes, but I think it should not matter in this case. cer@AmonLanc:/data/hoard> getfacl TheHoard/ # file: TheHoard/ # owner: john # group: cosas # flags: -s- user::rwx user:wwwrun:r-x group::rwx mask::rwx other::--- cer@AmonLanc:/data/hoard> cer@AmonLanc:/data/hoard> l TheHoard/ total 20 drwxrws---+ 6 john cosas 4096 Nov 1 2014 ./ drwxr-xr-x 5 root root 94 Sep 26 2014 ../ drwxr-s---+ 12 john cosas 4096 Oct 25 14:43 Asnos/ drwxr-s--- 2 john cosas 4096 Nov 1 2014 Asnos - Wrong file, unwanted or useless/ - -rwxr-x---+ 1 john cosas 449 Sep 26 2014 cambiar_acls_hoard* cer@AmonLanc:/data/hoard> cer@AmonLanc:/data/hoard> groups users root cosas cer@AmonLanc:/data/hoard> As you see, user "cer" on that machine can access the directory "TheHoard". Then, I mount that filesystem over nfs on another machine: server: cer@AmonLanc:/data/hoard> cat /etc/exports /data/hoard 192.168.1.0/24(fsid=2456,rw,root_squash,sync,nohide,no_subtree_check) cer@AmonLanc:/data/hoard> client: cer@Telcontar:/data/hoard> grep hoard /etc/fstab AmonLanc.valinor:/data/hoard/ /data/hoard nfs4 noauto,nofail,_netdev,user,users,relatime,acl 0 0 cer@Telcontar:/data/hoard> (acl I added minutes ago, to try if it makes a difference; it does not). Telcontar:~ # mount | grep /data/hoard AmonLanc.valinor:/data/hoard on /data/hoard type nfs4 (rw,nosuid,nodev,noexec,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.X,local_lock=none,addr=192.168.1.Y,_netdev,user) Telcontar:~ # Now look at what I get on the client: cer@Telcontar:/data/hoard> l total 100 drwxr-xr-x 5 root root 94 Sep 26 2014 ./ drwxr-xr-x 21 root root 4096 Sep 9 2014 ../ drwxrws--- 6 john cosas 4096 Nov 1 2014 TheHoard/ - -rw-r--r-- 1 root root 86165 May 24 2014 remote_log cer@Telcontar:/data/hoard> getfacl TheHoard/ # file: TheHoard/ # owner: john # group: cosas # flags: -s- user::rwx group::rwx other::--- cer@Telcontar:/data/hoard> groups users root wheel cosas cer@Telcontar:/data/hoard> l TheHoard/ ls: cannot open directory TheHoard/: Permission denied cer@Telcontar:/data/hoard> You see, the ACLS are not transmitted over NFS. And despite being in the group, which has rwx permission, I can not access. User "john" on client machine, has access. The same happens on another client machine. All of them run oS 13.1. What am I doing wrong? :-? Ideas? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlYs5k4ACgkQtTMYHG2NR9XH2ACdH1Gk7vA2pjVdtwdZ5BxBlntU Z6YAnjgF+6+eoSmhr7a7l4WRmW3bQnN3 =MEuX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 20

Re: [opensuse] Can't access a certain directory over nfs, group access problem.
by Carlos E. R. 26 Oct '15

26 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-10-26 18:40, Andrei Borzenkov wrote: > Sorry? Oh, my...! Sorry. Must be a Thunderbird/enigmail glitch. For some reason it automatically encrypted the message, instead of only signing. The plain message goes below. > > Отправлено с iPhone > >> 26 окт. 2015 г., в 20:06, Carlos E. R. >> <robin.listas(a)telefonica.net> написал(а): >> > On 2015-10-26 18:01, Andrei Borzenkov wrote: >> Oh, sorry, I see. Your user belongs to more than 16 groups. In >> this case it is random which groups will be used to >> authenticate. Apparently group that is required is missing. There >> is an option for RPC on server to ignore groups that client sends >> and use local groups on server; I cannot check right now. > > You mean there is a limit to the number of group a user can belong > to? I may be able to remove some. > - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlYueDoACgkQja8UbcUWM1zlxQEAg5aBntTzwVLe7bZRS/2pK/Bh QvzhRLIPmQVJnPWAfEcA/j1ks5F/4QsE3pecnZCTEZTHPd2sjyJpK3GV9n5k16ch =qVip -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] MS giving away Exchange 2016 -- trying to get foot in door
by Linda Walsh 26 Oct '15

26 Oct '15

http://www.microsoft.com/en-us/download/details.aspx?id=49161 ^^^ On their download site, I ran across a free download to run Exchange 2016. Doesn't say anything about it being a demo version or expiring... I guess not enough software out there is supporting the MS-TNEF (spelling?) that most non-ms clients don't understand. Anyway... if you wanted to play w/it for free, maybe stick it in a VM, thought I'd mention it. Though, FWIW, I think I'm sticking with dovecot for the foreseeable future... ;-) -l -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 12

[opensuse] marketing meeting 1017
by Douglas DeMaio 26 Oct '15

26 Oct '15

Hi all, We had a marketing meeting today for those who didn't attend the last one. The focus of this one was primarily on developing the wiki for Leap. Doing screenshots and listing the major features of Leap 42.1. We will do a wikithon next weekend Oct. 24 and 25 ad info about Leap to the portal - https://en.opensuse.org/Portal:42.1 I will publish an article on Monday on news.o.o with all the details. Enjoy our weekend. v/r Doug Meeting summary Hashtag (ddemaio, 16:02:13) #openSUSELeap (ddemaio, 16:02:28) Release party (ddemaio, 16:02:44) contact ddemaio for marketing material (ddemaio, 16:03:30) Release party info is at https://en.opensuse.org/openSUSE:Launch_parties please add your release party if you plan on doing one and let me now ASAP so I can mail and/or order some items for your release party (ddemaio, 16:07:47) slogan (ddemaio, 16:08:00) Messaging (ddemaio, 16:10:01) social media (ddemaio, 16:11:20) social media plan at https://en.opensuse.org/openSUSE:Social_media_launch_plan (ddemaio, 16:11:31) ACTION: once slogan is complete, sm plan can go for translation (ddemaio, 16:12:56) hackathon (ddemaio, 16:14:39) https://news.opensuse.org/ (Ada_Lovelace, 16:19:22) https://en.opensuse.org/Special:ActiveUsers (Ada_Lovelace, 16:21:24) track contributions @ https://en.opensuse.org/Special:ActiveUsers (ddemaio, 16:22:07) screenshots can be found at https://en.opensuse.org/Screenshots (ddemaio, 16:26:02) features is at https://en.opensuse.org/Features (ddemaio, 16:26:14) fine tune the portal https://en.opensuse.org/Portal:42.1 (ddemaio, 16:27:41) use wiki (ddemaio, 16:50:54) ACTION: publish article on new.o.o (ddemaio, 16:51:12) track contributions on wiki (ddemaio, 16:51:41) hackaton next weekend (ddemaio, 16:51:59) wikithon (ddemaio, 16:53:20) http://community.opensuse.org/meetings/opensuse-marketing/2015/opensuse-mar… -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] RE: MS giving away Exchange 2016 -- trying to get foot in door
by André Verwijs 26 Oct '15

26 Oct '15

why on this list..?? doesn't work on Linux, right?? André -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 18

[opensuse] Fosdem 2016
by Kostas Koudaras 26 Oct '15

26 Oct '15

Hi I haven't seen much movement about the upcoming FOSDEM. In 13 of November is the Deadline for Stands. As noone else jumped in so far I volunteeer to make arangements for the booth with the organizers again this year. Any thoughts? Have Fun Kostas -- --- \m/ --- If you're not failing every now and again, it's a sign you're not doing anything very innovative. --- \m/ --- me I am not I --- \m/ --- Time travel is possible, you just need to know the right aliens -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] SpiderOak now $12 for 1 TB of cloud backup
by Greg Freemyer 25 Oct '15

25 Oct '15

I just noticed SpiderOak has significantly dropped their price for cloud backup/sync storage. I've been paying $9 for 100GB. Nice to see I only jump to $12 when I fill that up. Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] mdraid array assemble problem
by Istvan Gabor 25 Oct '15

25 Oct '15

Hello: This occurs in openSUSE 12.2. I have several raid 1 devices most of them are 1.0 style. During boots the arrays are arbitrarily assembled. For example after first boot some of the arrays are assembled with one drive only. Even if I don't use/mount the devices and reboot the computer they are assembled differently after the new boot. It seems arbitrary which devices are assembled correctly and which not. It is arbitrary too which one of the mirror devices (/dev/sdbx or /dev/sdcx) become part of the array and which not. See the example: First boot: Personalities : [raid1] md1 : active (auto-read-only) raid1 sdb1[2] 20971520 blocks super 1.0 [2/1] [U_] md14 : active raid1 sdc14[2] sdb14[3] 62918468 blocks super 1.0 [2/2] [UU] md16 : active raid1 sdc16[2] sdb16[3] 62918468 blocks super 1.0 [2/2] [UU] md18 : active (auto-read-only) raid1 sdb18[0] 31455104 blocks super 1.0 [2/1] [U_] md8 : active raid1 sdc8[1] sdb8[0] 31438720 blocks super 1.2 [2/2] [UU] md9 : active raid1 sdc9[2] 62918468 blocks super 1.0 [2/1] [_U] md15 : active raid1 sdc15[2] sdb15[0] 62918468 blocks super 1.0 [2/2] [UU] md12 : active (auto-read-only) raid1 sdb12[0] 62918468 blocks super 1.0 [2/1] [U_] md11 : active (auto-read-only) raid1 sdb11[3] 62918468 blocks super 1.0 [2/1] [U_] md13 : active (auto-read-only) raid1 sdb13[3] 62918468 blocks super 1.0 [2/1] [U_] md10 : active raid1 sdb10[3] 62918468 blocks super 1.0 [2/1] [U_] md20 : active (auto-read-only) raid1 sdb20[0] 62918468 blocks super 1.0 [2/1] [U_] md22 : active (auto-read-only) raid1 sdb22[0] 55439552 blocks super 1.2 [2/1] [U_] md7 : active raid1 sdc7[3] 31455164 blocks super 1.0 [2/1] [_U] md6 : active raid1 sdb6[2] 20971520 blocks super 1.0 [2/1] [_U] md19 : active (auto-read-only) raid1 sdb19[0] 62918468 blocks super 1.0 [2/1] [U_] md17 : active (auto-read-only) raid1 sdb17[0] 62918468 blocks super 1.0 [2/1] [U_] md21 : active raid1 sdc21[2] sdb21[3] 48829464 blocks super 1.0 [2/2] [UU] unused devices: <none> You can see that in some /dev/mdx /dev/sdbx devices become part of the array, while in others /dev/sdbx devices become part of the array. If I restart the computer without touching any arrays, after next boot I get: Personalities : [raid1] md1 : active raid1 sdb1[2] sdc1[1] 20971520 blocks super 1.0 [2/2] [UU] md18 : active raid1 sdb18[0] sdc18[2] 31455104 blocks super 1.0 [2/2] [UU] md11 : active raid1 sdc11[2] sdb11[3] 62918468 blocks super 1.0 [2/2] [UU] md20 : active raid1 sdc20[2] sdb20[0] 62918468 blocks super 1.0 [2/2] [UU] md9 : active raid1 sdc9[2] 62918468 blocks super 1.0 [2/1] [_U] md16 : active raid1 sdb16[3] sdc16[2] 62918468 blocks super 1.0 [2/2] [UU] md21 : active raid1 sdc21[2] sdb21[3] 48829464 blocks super 1.0 [2/2] [UU] md6 : active raid1 sdb6[2] 20971520 blocks super 1.0 [2/1] [_U] md19 : active raid1 sdc19[2] sdb19[0] 62918468 blocks super 1.0 [2/2] [UU] md8 : active raid1 sdb8[0] sdc8[1] 31438720 blocks super 1.2 [2/2] [UU] md22 : active raid1 sdb22[0] sdc22[1] 55439552 blocks super 1.2 [2/2] [UU] md15 : active raid1 sdb15[0] sdc15[2] 62918468 blocks super 1.0 [2/2] [UU] md10 : active raid1 sdb10[3] 62918468 blocks super 1.0 [2/1] [U_] md7 : active raid1 sdc7[3] 31455164 blocks super 1.0 [2/1] [_U] md12 : active raid1 sdc12[2] sdb12[0] 62918468 blocks super 1.0 [2/2] [UU] md14 : active raid1 sdc14[2] sdb14[3] 62918468 blocks super 1.0 [2/2] [UU] md13 : active raid1 sdb13[3] sdc13[2] 62918468 blocks super 1.0 [2/2] [UU] md17 : active raid1 sdc17[2] sdb17[0] 62918468 blocks super 1.0 [2/2] [UU] unused devices: <none> A different assemble "pattern". And it goes like this from boot to boot. Why is this? How to fix this? Is this hardware of software issue? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 7

[opensuse] Scroll bar arrows
by Anton Aylward 25 Oct '15

25 Oct '15

I'm using KDE4 and even in the GTK applications like Thunderbird and Firefox the scrollbars on the far right have not just the up arrow (6) at the top of the scroll-bar and the down arrow (v) at the bottom but an extra up arrow at the bottom. I can see the utility of this. if you want to edge up and own without moving the cursor much its convenient. But I'm finding it an annoyance; my scrollbars are narrow so as to give the most space to the real information, and so these arrows are small. Its just too easy for me to click on the up at the bottom instead of the down. Is there some way to turn this extra up arrow off? There must be, but I can't find it. Can anyone help? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 8

[opensuse] Why do docs for 'ip' cmd differ from it's implementation (spec. use brd not broadcast)
by Linda Walsh 25 Oct '15

25 Oct '15

The main error I found (I don't know how many of these there are, as there doesn't seem to be a list of correspondences). But if you try to set to 'broadcast' address with ip addr, as documented in the manpage, as well as the output from "ip addr help", it won't work -- because broadcast is abbreviated 'brd'. The command won't take the unabbreviated form, and the *abbreviation*, 'brd' (for broadcast) isn't mentioned anywhere in the built-in 'ip' help, nor in the manpages. The problem here, as I look at the output of "ip addr help", It shows (showing partial output): > ip addr help Usage: ip address {add|change|replace} IFADDR dev IFNAME [ LIFETIME ] IFADDR := PREFIX | ADDR peer PREFIX [ broadcast ADDR ] [ anycast ADDR ] [ label IFNAME ] [ scope SCOPE-ID ] --- The problem is I don't know which terms like broadcast are abbreviated nor what their abbreviations would be. if brd=broadcast, does that mean 'any=anycast' or lbl=label, for example? In somecases -- under lifetime, they show the abbreviation: LIFETIME := [ valid_lft LFT | preferred_lft LFT ] --- Does anyone know if broadcast is they only flag that uses a non-truncation based abbreviation? (i.e. -- most of the terms will take the first few letters -- whatever uniquely defines it, except for: "ad" resolving to "address" -- theoretically it could be an abbreviation for "addrlabel" as well. "r"->route (not rule) "t"->tunnel (not token) and a few others where the 2nd-competing command probably came after the 1st. Anyway -- that 'broadcast' -> brd' took a while for me to figure out -- thus am a bit nervous about what other surprises might await me. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0