Re: sudumb

2017-07-24 Thread Macs R We 
I had a crapload of lines that begin with %:

> # Samples
> # %users  ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
> # %users  localhost=/sbin/shutdown -h now
> # %zimbra ALL=NOPASSWD:/opt/zimbra/libexec/zmstat-fd *
> # %zimbra   ALL=NOPASSWD:/opt/zimbra/openldap/libexec/slapd
> # %zimbra   ALL=NOPASSWD:/opt/zimbra/libexec/zmslapd
> # %zimbra ALL=NOPASSWD:/opt/zimbra/libexec/zmmailboxdmgr
> # %zimbra ALL=NOPASSWD:/opt/zimbra/bin/zmcertmgr
> # %zimbra   ALL=NOPASSWD:/opt/zimbra/postfix/sbin/postfix, 
> /opt/zimbra/postfix/sbin/postalias, /opt/zimbra/postfix/sbin/qshape.pl, 
> /opt/zimbra/postfix/sbin/postconf,/opt\
> /zimbra/postfix/sbin/postsuper
> # %zimbra   
> ALL=NOPASSWD:/opt/zimbra/libexec/zmqstat,/opt/zimbra/libexec/zmmtastatus
> # %everyone ALL=NOPASSWD: /Applications/Utilities/DeployStudio\ 
> Runtime.app/Contents/MacOS/DeployStudio\ 
> Runtime.bin,/Applications/Utilities/DeployStudio\ Admin.app/Cont\
> ents/Applications/DeployStudio\ Runtime.app/Contents/MacOS/DeployStudio\ 
> Runtime.bin

Only the first two (%users) were commented out to begin with.  All the rest 
were live and I had to comment them out.  

I don't even know what Zimbra is, I've never heard or or used anything with 
that name.  Apparently, it was something that belonged to Yahoo and VMWare at 
various times.  I did once own and run Fusion and Yahoo Mesenger, but I 
certainly never edited sudoers for either of them.

I do have something called DeployStudio in my Utilities.  I think I downloaded 
it when I was trying to create a boot server (never succeeded). Again, I 
certainly never edited sudoers for it.

Also from the post, whether you have problems with sudo or not seems to be 
dependent on whether you migrated your identity with Migration Assistant, which 
would copy over junk like old sudoers files from previous releases.


> On Jul 24, 2017, at 8:17 PM, David Schwartz  wrote:
> 
> On Jul 24, 2017, at 3:35 PM, Carl Hoefs  
> wrote:
>> 
>> See if this helps at all:
>> 
>> https://discussions.apple.com/thread/7906178?start=0&tstart=0
> 
> From the post:
> "Apple needs to fix this"
> 
> Fix what? None of my installations have a problem with sudo, and looking at 
> the sudoers file on a couple of random machines there is only one line that 
> begins with % :
> 
> %admin  ALL=(ALL) ALL
> 
> 
> Are people blaming Apple for changes or edits they've done themselves to this 
> file after installation? 
> 
> 
> 
>> 
>> -Carl
>> 
>> 
>>> On Jul 24, 2017, at 3:10 PM, Macs R We  wrote:
>>> 
>>> What would cause sudo to go deaf and dumb?
>>> 
>>> I updated to Sierra three days ago.  
>>> 
>>> I tried running a sudo command today and it just sits there like an idiot.  
>>> Never even asks for a password.
>>> 
>>> The day I updated to Sierra, I got notified that MailTags and GPG were 
>>> incompatible, so I updated both of them.  GPG still has only beta releases 
>>> if you need to run on Sierra (if they don't hurry, they're going to miss 
>>> Sierra entirely), so I installed that.  The installation hung when "one 
>>> minute to go" turned into 15+ minutes with still nothing happening.  
>>> Activity Monitor showed it hung in sudo, nothing apparent under sudo (but 
>>> for all I know, stuff under sudo forks its own hierarchy).  I quit and 
>>> retried it, with the same result; then tried uninstalling the whole thing 
>>> in case the old version was hosing something up; every installation or 
>>> deinstallation hung.  Several HOURS later, after I thought I had terminated 
>>> everything involved, a message popped up saying that either some 
>>> installation or deinstallation had actually finished, and enjoy the 
>>> results.  So I performed one final installation and let it run overnight; 
>>> it ultimately finished, or timed out and assumed it succeeded,
>  wh
>>> atever.  The point is, I don't know whether sudo was broken when GPG got 
>>> there, or GPG (or something I caused by aborting it) broke sudo, or what.
>>> 
>>> Anyway, is there some sort of stupid-lock that needs to be cleared to make 
>>> sudo proceed again?
>>> 
>>> I even went to console looking for sudo invocation entries.  Console and 
>>> its navigation is all changed in Sierra, and if it's still recording sudo 
>>> invocations I couldn't find them.
>>> ___
> 
> ___
> MacOSX-talk mailing list
> MacOSX-talk@omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/macosx-talk


___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Re: sudumb

2017-07-24 Thread David Schwartz 
On Jul 24, 2017, at 3:35 PM, Carl Hoefs  wrote:
> 
> See if this helps at all:
> 
> https://discussions.apple.com/thread/7906178?start=0&tstart=0

>From the post:
"Apple needs to fix this"

Fix what? None of my installations have a problem with sudo, and looking at the 
sudoers file on a couple of random machines there is only one line that begins 
with % :

%admin  ALL=(ALL) ALL


Are people blaming Apple for changes or edits they've done themselves to this 
file after installation? 



> 
> -Carl
> 
> 
>> On Jul 24, 2017, at 3:10 PM, Macs R We  wrote:
>> 
>> What would cause sudo to go deaf and dumb?
>> 
>> I updated to Sierra three days ago.  
>> 
>> I tried running a sudo command today and it just sits there like an idiot.  
>> Never even asks for a password.
>> 
>> The day I updated to Sierra, I got notified that MailTags and GPG were 
>> incompatible, so I updated both of them.  GPG still has only beta releases 
>> if you need to run on Sierra (if they don't hurry, they're going to miss 
>> Sierra entirely), so I installed that.  The installation hung when "one 
>> minute to go" turned into 15+ minutes with still nothing happening.  
>> Activity Monitor showed it hung in sudo, nothing apparent under sudo (but 
>> for all I know, stuff under sudo forks its own hierarchy).  I quit and 
>> retried it, with the same result; then tried uninstalling the whole thing in 
>> case the old version was hosing something up; every installation or 
>> deinstallation hung.  Several HOURS later, after I thought I had terminated 
>> everything involved, a message popped up saying that either some 
>> installation or deinstallation had actually finished, and enjoy the results. 
>>  So I performed one final installation and let it run overnight; it 
>> ultimately finished, or timed out and assumed it succeeded,
  wh
>> atever.  The point is, I don't know whether sudo was broken when GPG got 
>> there, or GPG (or something I caused by aborting it) broke sudo, or what.
>> 
>> Anyway, is there some sort of stupid-lock that needs to be cleared to make 
>> sudo proceed again?
>> 
>> I even went to console looking for sudo invocation entries.  Console and its 
>> navigation is all changed in Sierra, and if it's still recording sudo 
>> invocations I couldn't find them.
>> ___

___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Re: sudumb

2017-07-24 Thread Macs R We 
Yup, I just got done applying this fix and the "hang" (actually an incredibly 
long delay) went away.  Thanks.

> On Jul 24, 2017, at 3:35 PM, Carl Hoefs  
> wrote:
> 
> See if this helps at all:
> 
> https://discussions.apple.com/thread/7906178?start=0&tstart=0 
> 
> 
> -Carl
> 
> 
>> On Jul 24, 2017, at 3:10 PM, Macs R We > > wrote:
>> 
>> What would cause sudo to go deaf and dumb?
>> 
>> I updated to Sierra three days ago.  
>> 
>> I tried running a sudo command today and it just sits there like an idiot.  
>> Never even asks for a password.
>> 
>> The day I updated to Sierra, I got notified that MailTags and GPG were 
>> incompatible, so I updated both of them.  GPG still has only beta releases 
>> if you need to run on Sierra (if they don't hurry, they're going to miss 
>> Sierra entirely), so I installed that.  The installation hung when "one 
>> minute to go" turned into 15+ minutes with still nothing happening.  
>> Activity Monitor showed it hung in sudo, nothing apparent under sudo (but 
>> for all I know, stuff under sudo forks its own hierarchy).  I quit and 
>> retried it, with the same result; then tried uninstalling the whole thing in 
>> case the old version was hosing something up; every installation or 
>> deinstallation hung.  Several HOURS later, after I thought I had terminated 
>> everything involved, a message popped up saying that either some 
>> installation or deinstallation had actually finished, and enjoy the results. 
>>  So I performed one final installation and let it run overnight; it 
>> ultimately finished, or timed out and assumed it succeeded, wh
>> atever.  The point is, I don't know whether sudo was broken when GPG got 
>> there, or GPG (or something I caused by aborting it) broke sudo, or what.
>> 
>> Anyway, is there some sort of stupid-lock that needs to be cleared to make 
>> sudo proceed again?
>> 
>> I even went to console looking for sudo invocation entries.  Console and its 
>> navigation is all changed in Sierra, and if it's still recording sudo 
>> invocations I couldn't find them.
>> ___
>> MacOSX-talk mailing list
>> MacOSX-talk@omnigroup.com 
>> http://www.omnigroup.com/mailman/listinfo/macosx-talk
> 

___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Re: sudumb

2017-07-24 Thread Carl Hoefs 
See if this helps at all:

https://discussions.apple.com/thread/7906178?start=0&tstart=0 


-Carl


> On Jul 24, 2017, at 3:10 PM, Macs R We  wrote:
> 
> What would cause sudo to go deaf and dumb?
> 
> I updated to Sierra three days ago.  
> 
> I tried running a sudo command today and it just sits there like an idiot.  
> Never even asks for a password.
> 
> The day I updated to Sierra, I got notified that MailTags and GPG were 
> incompatible, so I updated both of them.  GPG still has only beta releases if 
> you need to run on Sierra (if they don't hurry, they're going to miss Sierra 
> entirely), so I installed that.  The installation hung when "one minute to 
> go" turned into 15+ minutes with still nothing happening.  Activity Monitor 
> showed it hung in sudo, nothing apparent under sudo (but for all I know, 
> stuff under sudo forks its own hierarchy).  I quit and retried it, with the 
> same result; then tried uninstalling the whole thing in case the old version 
> was hosing something up; every installation or deinstallation hung.  Several 
> HOURS later, after I thought I had terminated everything involved, a message 
> popped up saying that either some installation or deinstallation had actually 
> finished, and enjoy the results.  So I performed one final installation and 
> let it run overnight; it ultimately finished, or timed out and assumed it 
> succeeded, wh
> atever.  The point is, I don't know whether sudo was broken when GPG got 
> there, or GPG (or something I caused by aborting it) broke sudo, or what.
> 
> Anyway, is there some sort of stupid-lock that needs to be cleared to make 
> sudo proceed again?
> 
> I even went to console looking for sudo invocation entries.  Console and its 
> navigation is all changed in Sierra, and if it's still recording sudo 
> invocations I couldn't find them.
> ___
> MacOSX-talk mailing list
> MacOSX-talk@omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/macosx-talk

___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk

sudumb

2017-07-24 Thread Macs R We 
What would cause sudo to go deaf and dumb?

I updated to Sierra three days ago.  

I tried running a sudo command today and it just sits there like an idiot.  
Never even asks for a password.

The day I updated to Sierra, I got notified that MailTags and GPG were 
incompatible, so I updated both of them.  GPG still has only beta releases if 
you need to run on Sierra (if they don't hurry, they're going to miss Sierra 
entirely), so I installed that.  The installation hung when "one minute to go" 
turned into 15+ minutes with still nothing happening.  Activity Monitor showed 
it hung in sudo, nothing apparent under sudo (but for all I know, stuff under 
sudo forks its own hierarchy).  I quit and retried it, with the same result; 
then tried uninstalling the whole thing in case the old version was hosing 
something up; every installation or deinstallation hung.  Several HOURS later, 
after I thought I had terminated everything involved, a message popped up 
saying that either some installation or deinstallation had actually finished, 
and enjoy the results.  So I performed one final installation and let it run 
overnight; it ultimately finished, or timed out and assumed it succeeded, wh
 atever.  The point is, I don't know whether sudo was broken when GPG got 
there, or GPG (or something I caused by aborting it) broke sudo, or what.

Anyway, is there some sort of stupid-lock that needs to be cleared to make sudo 
proceed again?

I even went to console looking for sudo invocation entries.  Console and its 
navigation is all changed in Sierra, and if it's still recording sudo 
invocations I couldn't find them.
___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Re: Best way to duplicate a directory on a mac?

2017-07-24 Thread Carl Hoefs 

> On Jul 24, 2017, at 8:32 AM, Michael  wrote:
> 
> 
> On Jul 23, 2017, at 11:55 AM, Michael  wrote:
> 
> What is the best way to duplicate a directory tree on a mac?
>>> 
>>> Considering that my first attempt failed to account for all 5 timestamps 
>>> (remember, only 3 are seen by unix programs, but finder wants to show you 
>>> last opened and date added, and those are NOT atime and ctime), I went back 
>>> and did a time machine copy.
>>> 
>>> Still in backup; I'll have a restore ready to look at in the morning
> 
> Well, it turns out that even Time Machine cannot restore Date Added. It does 
> restore last opened. I did not check ctime, but I figure if anything can set 
> that, TM will.
> 
> And my previously-full 1 TB partition of data is now living comfortably on a 
> 1.7 TB partition.

In the past I've used rsync(1) to do this sort of thing, but I don't recall if 
it retains all the metadata you want..
-Carl

___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk

Re: Best way to duplicate a directory on a mac?

2017-07-24 Thread Michael 

 On Jul 23, 2017, at 11:55 AM, Michael  wrote:
 
 What is the best way to duplicate a directory tree on a mac?
>> 
>> Considering that my first attempt failed to account for all 5 timestamps 
>> (remember, only 3 are seen by unix programs, but finder wants to show you 
>> last opened and date added, and those are NOT atime and ctime), I went back 
>> and did a time machine copy.
>> 
>> Still in backup; I'll have a restore ready to look at in the morning

Well, it turns out that even Time Machine cannot restore Date Added. It does 
restore last opened. I did not check ctime, but I figure if anything can set 
that, TM will.

And my previously-full 1 TB partition of data is now living comfortably on a 
1.7 TB partition.

---
Entertaining minecraft videos
http://YouTube.com/keybounce

___
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk