* continued acl problems @ 2018-09-07 21:14 L A Walsh 2018-09-07 21:35 ` Andrey Repin 0 siblings, 1 reply; 4+ messages in thread From: L A Walsh @ 2018-09-07 21:14 UTC (permalink / raw) To: cygwin I'm now getting errors where I never got errors before -- this may be for the 'Trusted installer' user, or possibly domain users that I I tried copying files using tar|tar...I have a script that I've tried to run daily (but only do it manually), called 'daily_maint.sh' Tries to recycle old archive and tmp files as well as running disk cleanup. The log shows several problems: Moving old tmp files into Recycled/20180907133214 tar: Removing leading `/' from member names tar: tmp/05F831D4-6E5E-407A-A6CA-16FF47DDD8AA/en-US: Warning: Cannot acl_from_text: Invalid argument tar: tmp/05F831D4-6E5E-407A-A6CA-16FF47DDD8AA: Warning: Cannot acl_from_text: Invalid argument tar: tmp/51DD5395-10EE-4A95-9552-6E319B83C2BF/en-US: Warning: Cannot acl_from_text: Invalid argument tar: tmp/51DD5395-10EE-4A95-9552-6E319B83C2BF: Warning: Cannot acl_from_text: Invalid argument tar: tmp: Warning: Cannot acl_from_text: Invalid argument In all of these cases it appears that the problem is with directories. At first thought it was related to presence of 'TRUSTED USER' But I saw some 'flakeyness' on domain ID's, where I saw it display the correct text for them, but scrolling down to look for problems, and back up had the permissions dialog showing the raw numbers for my domain ID's, but scrolling again showed them as Domain\ID. So that's something to consider -- if there is a momentary flake in the resolution, it might cause a prob....just tried those files again. the "tmp/05" and "tmp/51..." No errors. Did something else change besides these probs you looked at? I have to stress...I've never seen the Cannot_acl_to_text message before my reporting it a week or so ago.... saw instances in use of 'tar' and 'rsync' at this point. I have seen similar messages out of rsync copying from a windows dir to a samba dir -- I figured local ID didn't exist on the remote samba dir. But have never seen it going between win-directories on the same machine...that's the new "problem", with current symptoms seeming to be limited to directories (maybe due to 2 acls)... Have never had these msgs going from win<->win on same machine. Sigh... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: continued acl problems 2018-09-07 21:14 continued acl problems L A Walsh @ 2018-09-07 21:35 ` Andrey Repin 2018-09-07 23:08 ` L A Walsh 0 siblings, 1 reply; 4+ messages in thread From: Andrey Repin @ 2018-09-07 21:35 UTC (permalink / raw) To: L A Walsh, cygwin Greetings, L A Walsh! > In all of these cases it appears that the problem is with directories. > At first thought it was related to presence of 'TRUSTED USER' > But I saw some 'flakeyness' on domain ID's, > where I saw it display the correct text for them, > but scrolling down to look for problems, and back up had the > permissions dialog showing the raw numbers for my domain ID's, but > scrolling again showed them as Domain\ID. Do you have cygserver running? > So that's something to consider -- if there is a momentary flake > in the resolution, it might cause a prob....just tried those files > again. the "tmp/05" and "tmp/51..." > No errors. > Did something else change besides these probs you looked at? > I have to stress...I've never seen the Cannot_acl_to_text > message before my reporting it a week or so ago.... > saw instances in use of 'tar' and 'rsync' at this point. > I have seen similar messages out of rsync copying from a windows > dir to a samba dir -- I figured local ID didn't exist on the > remote samba dir. > But have never seen it going between win-directories on the same > machine...that's the new "problem", with current symptoms seeming > to be limited to directories (maybe due to 2 acls)... > Have never had these msgs going from win<->win on same > machine. -- With best regards, Andrey Repin Saturday, September 8, 2018 0:25:37 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: continued acl problems 2018-09-07 21:35 ` Andrey Repin @ 2018-09-07 23:08 ` L A Walsh 2018-09-08 0:35 ` Andrey Repin 0 siblings, 1 reply; 4+ messages in thread From: L A Walsh @ 2018-09-07 23:08 UTC (permalink / raw) To: cygwin On 9/7/2018 2:26 PM, Andrey Repin wrote: > Greetings, L A Walsh! > >> In all of these cases it appears that the problem is with directories. > >> At first thought it was related to presence of 'TRUSTED USER' > >> But I saw some 'flakeyness' on domain ID's, >> where I saw it display the correct text for them, >> but scrolling down to look for problems, and back up had the >> permissions dialog showing the raw numbers for my domain ID's, but >> scrolling again showed them as Domain\ID. > > Do you have cygserver running? ---- Well....rt now, not sure...hmmm I should have had it running, as it's part of my startXwin.sh script which I run manually at start of every session, but did an update and had to kill off most or all of the cygstuff. But restarted 'X', which used to -- should have restarted it but, looking didn't see it in process list and trying the same command manually gave an error: > cygrunsrv -n -O -S -d messagebus cygserver cygrunsrv: --neverexits is only allowed with --install So I look at help and install is for installing a new service So I look at what services are installed: > cygrunsrv.exe -L cygserver messagebus syslogd Looks like the cygserver is already installed... Looking in the services control panel, I see cygserver, messagebus and syslogd, but syslogd won't stay running. Since I just ran the cygrunsrv command above, not sure if that started it or not. If I specify two services on the command line, should it have started both? with the same 'cygrunsrv'? They are set to start on system boot, but after the cyg-upgrade, they were likely killed and restarting 'X' likely didn't restart anything because of the error. Because cygserver won't let you start syslogd unless stderr isn't a TTY, I have to send cygserver's error off to /dev/null, so I wouldn't have seen any errors. So...am guessing it wasn't running, but may be now (not sure why syslogd isn't running -- will have to check that out later. But for now, will have to see if this reoccurs .... Thanks for the possible cause! ;-) Gotta love SW! -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: continued acl problems 2018-09-07 23:08 ` L A Walsh @ 2018-09-08 0:35 ` Andrey Repin 0 siblings, 0 replies; 4+ messages in thread From: Andrey Repin @ 2018-09-08 0:35 UTC (permalink / raw) To: L A Walsh, cygwin Greetings, L A Walsh! >>> In all of these cases it appears that the problem is with directories. >> >>> At first thought it was related to presence of 'TRUSTED USER' >> >>> But I saw some 'flakeyness' on domain ID's, >>> where I saw it display the correct text for them, >>> but scrolling down to look for problems, and back up had the >>> permissions dialog showing the raw numbers for my domain ID's, but >>> scrolling again showed them as Domain\ID. >> >> Do you have cygserver running? > ---- > Well....rt now, not sure...hmmm If you see them in service manager, then I'm curious by your observed behavior. cygserver's one effect is to stabilize SID resolution within a session. And yes, you should not be starting cygserver manually, unless for testing purposes. I have no idea, what effect would have multiple cygserver's running in the same system. > I should have had it running, as it's part of my startXwin.sh > script which I run manually at start of every session, but > did an update and had to kill off most or all of the cygstuff. > But restarted 'X', which used to -- should have restarted > it but, looking didn't see it in process list and trying the > same command manually gave an error: >> cygrunsrv -n -O -S -d messagebus cygserver > cygrunsrv: --neverexits is only allowed with --install > So I look at help and install is for installing a new service > So I look at what services are installed: >> cygrunsrv.exe -L > cygserver > messagebus > syslogd > Looks like the cygserver is already installed... > Looking in the services control panel, I see cygserver, > messagebus and syslogd, but syslogd won't stay running. > Since I just ran the cygrunsrv command above, not sure if that > started it or not. > If I specify two services on the command line, should it > have started both? with the same 'cygrunsrv'? They are set > to start on system boot, but after the cyg-upgrade, they were > likely killed and restarting 'X' likely didn't restart anything > because of the error. > Because cygserver won't let you start syslogd unless stderr > isn't a TTY, I have to send cygserver's error off to /dev/null, > so I wouldn't have seen any errors. > So...am guessing it wasn't running, but may be now (not sure > why syslogd isn't running -- will have to check that out later. > But for now, will have to see if this reoccurs .... > Thanks for the possible cause! ;-) -- With best regards, Andrey Repin Saturday, September 8, 2018 3:23:39 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-09-08 0:35 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-09-07 21:14 continued acl problems L A Walsh 2018-09-07 21:35 ` Andrey Repin 2018-09-07 23:08 ` L A Walsh 2018-09-08 0:35 ` Andrey Repin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).