Error with command "sudo: /etc/sudoers is mode 0777, should be 0440 Segmentation fault"

I don't know what to do... I installed XAMPP for Mac and then Joomla, I had some problems and I changed the permissions to some folders, so everything was working well, later I turned off my MacBook and when turned on some parts of Joomla was not working (http://localhost/administrator) neither MySQL Server (http://localhost/phpmyadmin), so I entered to a console and I tried to change the permissions again but when I try to be superuser I can't, the error that means is:
sudo: /etc/sudoers is mode 0777, should be 0440 Segmentation fault
Sorry, I don't speak english, I tried to explain my error the better i could.

What is an SO disk? Do you mean your install disks? If so, don't use them. Run Disk Utility from your hard drive. The only time you should run Disk Utility from an install disk is when you need to repair the filesystem. When running Repair Permissions, it should be run from your hard drive so that the permissions it fixes correspond with your updated OS version.

Similar Messages

Using sudo gives "/etc/sudoers is mode 0640, should be 0440" error...

I tried to edit the sudoers file and must have done something wrong. Every time I try to use the sudo command I get the following two errors:
sudo: /etc/sudoers is mode 0640, should be 0440
and
Segmentation fault
I'm a new user. Any ideas on how I can get things fixed up again so that I can use sudo again?
Thanks in advance.

Solved the issue by running the *Disk Utility* and running the *Repair Permissions* command.

Problem with sudo - sudoers is mode 0604, should be 0440

ryans-imac-2:~ Ryan$ sudo chmod -RN /.vol
sudo: /private/etc/sudoers is mode 0604, should be 0440
ryans-imac-2:~ Ryan$ postdrop: warning: unable to look up public/pickup: No such file or directory
Please advise.

There is a '-N' option for chmod -- it's for removing ACL's.
The best way to learn is not to make random changes that you don't understand, and then ask for help in public forums when something goes wrong. Set yourself a constructive problem to solve; for instance, by writing a shell script. Read man pages. Read UNIX books.
You say you want to grant permissions to the current user. Which permissions -- read, write, execute, all? Do you mean ownership? ACL's? Recursive? Sticky or SUID bits? What permissions should other users have? First learn how to ask the right question, then you'll most likely be able to answer it yourself. Start with the chmod(1) man page. When you understand everything on that page, you'll know quite a lot.
Meanwhile you might be able to repair the damage you'be already done by running the "Repair permissions" routine from Disk Utility. This would be one of the few situations where it's actually useful.

Mode 0660, should be 0440 error

trying to run sudo -s
getting error "sudo: /etc/sudoers is mode 0660, should be 0440"
root is enabled on this Snow Leopard Macbook Pro
try to change it by issueing:
sudo chmod 440 /etc/sudoers
gets the same error
I only want to fix this error, not dissect why Im doing this or that, if you dont know the cause and resolution, please dont reply

If 'root' is really enabled, and you know the root password, then just use the command:
su
Password ...enter root password here...
chmod 440 /etc/sudoers
You could try Disk Utility Repair Permissions. Maybe that would fix the sudoers file (I do not know if it will, but it is worth a try). If Disk Utility will not run because it too needs a working sudoers file, then boot from the installation DVD and run Disk Utility from there.
Failing that you could boot your Mac holding the 'T' key so you get into "Target" mode, and using firewire cable, mount your Mac on another Mac and use the other Mac to fix the /Volumes/yourMacsMountName/etc/sudoers file permission.
Next would be booting into single user mode, and I think then using "mount -u" to get your boot disk writable, and then applying the "chmod 440".
And in the future use the "visudo" command to make any /etc/sudoers file modifications (see man sudoers).

How to fix AppleEvent handler failed error with command "make new mailbox with properties"

Below is the script I am running to create a hiearchy of new mailboxes inside "ON MY MAC" folder area.
tell application "Mail"
make new mailbox with properties {name:"ABar"}
make new mailbox with properties {name:"ABar/Foo"}
make new mailbox with properties {name:"ABar/Foo/Me"}
end tell
When I execute this the first mailbox is excuted fine but right afterwards I get the following error:
error "Mail got an error: AppleEvent handler failed." number -10000
I have tried adding delays but this does not work either. Code:
tell application "Mail"
make new mailbox with properties {name:"ABar"}
delay 0.2
make new mailbox with properties {name:"ABar/Foo"}
          delay 0.2
make new mailbox with properties {name:"ABar/Foo/Me"}
end tell
However rerunning the script and skipping over the make command if the folder already exit, causes the next exuction time to create one more folder.
Code:
tell application "Mail"
          if (mailbox "ABar" exists) = false then
make new mailbox with properties {name:"ABar"}
                    delay 0.2
          end if
          if (mailbox "ABar/Foo" exists) = false then
make new mailbox with properties {name:"ABar/Foo"}
                    delay 0.2
          end if
          if (mailbox "ABar/Foo/Me" exists) = false then
make new mailbox with properties {name:"ABar/Foo/Me"}
                    delay 0.2
          end if
end tell
** Anyone know how to solve this or why this is happening? **
It almost feels as if the hiearcgy is read into memory and this is not updated after the creation of the new mailbox.
Thanks!

Hi,
The processors are different archiectures and you can not use binaries from one architecture to work on the other.
Library name suffix differences is an example of the importance of this. Tuxedo 6.5 was separately built for each of those architectures and
is available on the PeopleSoft distribution as distinct binaries. If your migration was purely from HPUX11.11 to HPUX11.23 you might have
succeeded but the processor difference will not work for you and a core dump would not be unexpected.
Bob Finan
FYI:
Tuxedo 6.5 is end-of-lifed and, since it's EOL has passed the stage for extended support possibility, no new patches will
be created for it by engineering. You should look to migrate to a newer version of Tuxedo/Peoplesoft at the earliest
possiblity.

Encounter error with command "New-MailboxFolder" (The specified mailbox doesn't exist)

[Symptom]
======================
Generally, a user can use “New-MailboxFolder” command to create mailbox folder for his own mailbox successfully. See the following example:
The above command creates a new folder named “PersonalFAQ” in the mailbox of Administrator.
However, this command cannot be used to create folders on other user’s mailbox although the full access permission is assigned. See the follow example. (We already granted the full access permission of
test1 user to administrator user)
Just as what the picture shows, an error message will appear:
“The specified mailbox “username” doesn’t exist.”
[Cause Analysis]
=======================================
It’s by default. The “New-MailboxFolder” command cannot be used to create folders for other mailboxes.
[Workarounds]
==============================
1. Use EWS channel to create the folders for other mailboxes.
http://msdn.microsoft.com/en-us/library/office/dn535504(v=exchg.150).aspx#bk_createfolderewsma
2. Use MFCMAPI:
3. PFDAVADMIN (Exchange 2003/2007) or Exfolders (Exchange 2010)
More information:
Creating Folders (Exchange Web Services)
http://msdn.microsoft.com/en-us/library/office/aa563302(v=exchg.140).aspx
New-MailboxFolder
http://technet.microsoft.com/en-us/library/dd335113(v=exchg.150).aspx
Microsoft Exchange Server MAPI Editor
http://www.microsoft.com/en-gb/download/details.aspx?id=2953
Exchange 2010 SP1 (and later) ExFolders
http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Since this issue is related to only one user, this means that the USERPARAMS information for this user is corrupted.
The issue could be resolved by deleting all entries related to this user on this table on the HFM DB.
Kindly open the HFM DB and look for the <application name>_userparams table.
and,
Delete the enteries corresponding to the user.Backup this table prior truncating the table.Please get this operation done by an administrator.
Edited by: user10931567 on 16-Jul-2009 10:03 AM

Audio Buffer error with command line app

I run a program called SBAGEN, which is a binaural beat frequency program that runs from Terminal.app - lately, when I invoke one of the scripts for this program, I get this error:
Set audio output buffer size failed, status = 1852797029
any ideas as to how to solve this?
Thanks

Resolved this issue on my own:
*SYSTEM PREF—-> SOUND —–> SOUND EFFECTS*
I needed to make sure that under +SOUND EFFECTS+, that the following was selected in the drop down menu +“Play sounds and alerts from”+: *SELECTED SOUND OUTPUT DEVICE*

Error with sdl_mixer [Solved]

Tried in install tux paint but it did not work very well so removed it. Then started getting errors with pacman
sudo pacman -S sdl_mixer
warning: sdl_mixer-1.2.12-3 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (1): sdl_mixer-1.2.12-3
Total Installed Size: 0.21 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [------------------------------------------------------------] 100%
error: sdl_mixer: signature from "Jan Alexander Steffens (heftig) <[email protected]>" is invalid
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Keys are up to date....
Now I am getting these messages when using pacman
warning: atop-2.0_1-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (1): atop-2.0_1-1
Total Download Size: 0.09 MiB
Total Installed Size: 0.48 MiB
Net Upgrade Size: 0.00 MiB
Proceed with installation? [Y/n] y
:: Retrieving packages from community...
atop-2.0_1-1-x86_64 88.7 KiB 618K/s 00:00 [------------------------------------------------------------] 100%
(1/1) checking package integrity [------------------------------------------------------------] 100%
(1/1) loading package files [------------------------------------------------------------] 100%
(1/1) checking for file conflicts [------------------------------------------------------------] 100%
(1/1) checking available disk space [------------------------------------------------------------] 100%
(1/1) upgrading atop [------------------------------------------------------------] 100%
ldconfig: File /usr/lib/libSDL_ttf-2.0.so.0.10.1 is empty, not checked.
ldconfig: File /usr/lib/libsmpeg-0.4.so.0.1.3 is empty, not checked.
ldconfig: File /usr/lib/libmikmod.so.3 is empty, not checked.
ldconfig: File /usr/lib/libpaper.so.1 is empty, not checked.
ldconfig: File /usr/lib/libpaper.so.1.1.2 is empty, not checked.
ldconfig: File /usr/lib/libSDL_mixer-1.2.so.0.12.0 is empty, not checked.
ldconfig: File /usr/lib/libmikmod.so is empty, not checked.
ldconfig: File /usr/lib/libSDL_mixer-1.2.so.0 is empty, not checked.
ldconfig: File /usr/lib/libmikmod.so.3.0.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_ttf-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_Pango.so.1 is empty, not checked.
ldconfig: File /usr/lib/libsmpeg.so is empty, not checked.
ldconfig: File /usr/lib/libSDL_ttf.so is empty, not checked.
ldconfig: File /usr/lib/libSDL_Pango.so is empty, not checked.
ldconfig: File /usr/lib/libpaper.so is empty, not checked.
ldconfig: File /usr/lib/libsmpeg-0.4.so.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_Pango.so.1.1.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_mixer.so is empty, not checked.
Any ideas on what I have done wrong?
Last edited by heman (2013-02-03 11:07:22)

Targets (7): ntfs-3g-2013.1.13-1 ntfsprogs-2013.1.13-1 speex-1.2rc1-3 sudo-1.8.6.p6-1 xorg-sessreg-1.0.7-2 xorg-xdpyinfo-1.3.0-2 xorg-xset-1.2.2-2
Total Download Size: 1.52 MiB
Total Installed Size: 5.05 MiB
Net Upgrade Size: 0.02 MiB
Proceed with installation? [Y/n] y
:: Retrieving packages from core...
sudo-1.8.6.p6-1-x86_64 576.4 KiB 2.08M/s 00:00 [------------------------------------------------------------] 100%
:: Retrieving packages from extra...
ntfs-3g-2013.1.13-1-x86_64 253.7 KiB 7.16M/s 00:00 [------------------------------------------------------------] 100%
ntfsprogs-2013.1.13-1-x86_64 150.4 KiB 6.96M/s 00:00 [------------------------------------------------------------] 100%
speex-1.2rc1-3-x86_64 536.7 KiB 7.65M/s 00:00 [------------------------------------------------------------] 100%
xorg-sessreg-1.0.7-2-x86_64 7.5 KiB 10.8M/s 00:00 [------------------------------------------------------------] 100%
xorg-xdpyinfo-1.3.0-2-x86_64 14.0 KiB 16.7M/s 00:00 [------------------------------------------------------------] 100%
xorg-xset-1.2.2-2-x86_64 16.9 KiB 16.1M/s 00:00 [------------------------------------------------------------] 100%
(7/7) checking package integrity [------------------------------------------------------------] 100%
(7/7) loading package files [------------------------------------------------------------] 100%
(7/7) checking for file conflicts [------------------------------------------------------------] 100%
(7/7) checking available disk space [------------------------------------------------------------] 100%
(1/7) upgrading ntfs-3g [------------------------------------------------------------] 100%
(2/7) upgrading ntfsprogs [------------------------------------------------------------] 100%
(3/7) upgrading speex [------------------------------------------------------------] 100%
(4/7) upgrading sudo [------------------------------------------------------------] 100%
(5/7) upgrading xorg-sessreg [------------------------------------------------------------] 100%
(6/7) upgrading xorg-xdpyinfo [------------------------------------------------------------] 100%
(7/7) upgrading xorg-xset [------------------------------------------------------------] 100%
ldconfig: File /usr/lib/libSDL_ttf-2.0.so.0.10.1 is empty, not checked.
ldconfig: File /usr/lib/libsmpeg-0.4.so.0.1.3 is empty, not checked.
ldconfig: File /usr/lib/libmikmod.so.3 is empty, not checked.
ldconfig: File /usr/lib/libpaper.so.1 is empty, not checked.
ldconfig: File /usr/lib/libpaper.so.1.1.2 is empty, not checked.
ldconfig: File /usr/lib/libSDL_mixer-1.2.so.0.12.0 is empty, not checked.
ldconfig: File /usr/lib/libmikmod.so is empty, not checked.
ldconfig: File /usr/lib/libSDL_mixer-1.2.so.0 is empty, not checked.
ldconfig: File /usr/lib/libmikmod.so.3.0.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_ttf-2.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_Pango.so.1 is empty, not checked.
ldconfig: File /usr/lib/libsmpeg.so is empty, not checked.
ldconfig: File /usr/lib/libSDL_ttf.so is empty, not checked.
ldconfig: File /usr/lib/libSDL_Pango.so is empty, not checked.
ldconfig: File /usr/lib/libpaper.so is empty, not checked.
ldconfig: File /usr/lib/libsmpeg-0.4.so.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_Pango.so.1.1.0 is empty, not checked.
ldconfig: File /usr/lib/libSDL_mixer.so is empty, not checked.
Ok removed sdl_mixer from cache, but after update now get above

Download does not start, error with order

i've been trying to dowload lightroom 4 for more than a week. the download does not start and when i try to buy the program i get a "error with your order message" any idea what i should try next??

MichaelAShea which web browser are you using? Please try a different web browser. If you continue to face difficulties then I would recommend installing via the Creative Cloud Desktop application. You can find more details at Install and update apps - https://helpx.adobe.com/creative-cloud/help/install-apps.html.

Segmentation fault when using snapshot isolation with Berkeley DB 6.1.19 and 5.1.29

Hello,
I have been experimenting with snapshot isolation with Berkeley DB, but I find that it frequently triggers a segmentation fault when write transactions are in progress. The following test program reliably demonstrates the problem in Linux using either 5.1.29 or 6.1.19.
https://anl.app.box.com/s/3qq2yiij2676cg3vkgik
Compilation instructions are at the top of the file. The test program creates a temporary directory in /tmp, opens a new environment with the DB_MULTIVERSION flag, and spawns 8 threads. Each thread performs 100 transactional put operations using DB_TXN_SNAPSHOT. The stack trace when the program crashes generally looks like this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7483700 (LWP 11871)]
0x00007ffff795e190 in __memp_fput ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
(gdb) where
#0 0x00007ffff795e190 in __memp_fput ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#1 0x00007ffff7883c30 in __bam_get_root ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#2 0x00007ffff7883dca in __bam_search ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#3 0x00007ffff7870246 in ?? () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#4 0x00007ffff787468f in ?? () from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#5 0x00007ffff79099f4 in __dbc_iput ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#6 0x00007ffff7906c10 in __db_put ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#7 0x00007ffff79191eb in __db_put_pp ()
   from /usr/lib/x86_64-linux-gnu/libdb-5.1.so
#8 0x0000000000400f14 in thread_fn (foo=0x0)
    at ../tests/transactional-osd/bdb-snapshot-write.c:154
#9 0x00007ffff7bc4182 in start_thread (arg=0x7ffff7483700)
    at pthread_create.c:312
#10 0x00007ffff757f38d in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
I understand that this test program, with 8 concurrent (and deliberately conflicting) writers, is not an ideal use case for snapshot isolation, but this can be triggered in other scenarios as well.
You can disable snapshot isolation by toggling the value of the USE_SNAP #define near the top of the source, and the test program then runs fine without it.
Can someone help me to identify the problem?
many thanks,
-Phil

Hi Phil,
   We have taken a look at this in more detail and there was a bug in the code.   We have fixed the bug.     We will roll it into our next 6.1 release that we do.   If you would like an early patch that will go on top of 6.1.19, please email me at [email protected], reference this forum post and I can get a patch sent out to you.   It will be a .diff file that apply on the source code and then rebuild the library. Once again thanks for finding the issue, and providing a great test program which tremendously helped in getting this resolved.
thanks
mike

[SOLVED] Unable to use SUDO: issues with /etc/sudoers

I have reinstalled Arch_64 and I have run into some problems with SUDO.
I get the following errors when I try to use sudo:
sudo : unable to stat /etc/sudoers : Permission Denied
sudo : no valid sudoers sources found, quitting
sudo : unable to initialize policy plugin
Here's what I have done with it so far:
* I added USERNAME (myself) to the 'wheel' group
* I uncommented %wheel ALL=(ALL) All using visudo
As it was not working for me I also:
* # chown -c root:root /etc/sudoers
* # chmod -c 0440 /etc/sudoers
* Since that too did not work, I recommented %wheel and added USERNAME ALL=(ALL) ALL just under the line root ALL=(ALL) ALL and repeated the above steps. The above problem persists.
* I checked with visudo -c and it says "/etc/sudoers parsed ok".
I have been through the WIKI and the forums but still unable to figure out whats going wrong.
I will appreciate if the forum can guide me to solution and help me resolve this issue.
Thanks.
Last edited by fantab (2012-11-20 09:00:56)

Had exactly the same problem with a new Arch_64 install a few months ago, which turned out to be a problem with permissions on / (which i changed with chmod) - can't remember the details, but it was this post that put me on to a solution:
http://archlinuxarm.org/forum/viewtopic … =20#p19727

I am trying to install oracle 11g xe on ubuntu aws instance when i execute sudo /etc/init.d/oracle-xe configure command iam getting this error: sudo: /etc/init.d/oracle-xe : command not found

i am trying to install oracle 11g xe on ubuntu aws instance when i execute sudo /etc/init.d/oracle-xe configure command iam getting this error: sudo: /etc/init.d/oracle-xe : command not found.

"command not found" means ... there is no such thing.
Has the .rpm been installed?
http://docs.oracle.com/cd/E17781_01/install.112/e18802/toc.htm#XEINL122

Sudo: unable to stat /etc/sudoers: No such file or directory sudo: no valid sudoers sources found, quitting

I am trying to empty my trash but it wouldn't . so I ran this command sudo rm -rf ~/.Trash/* in the terminal
I got an error message
"sudo: unable to stat /etc/sudoers: No such file or directory
sudo: no valid sudoers sources found, quitting"
does anyone have a clue? thanks

First, never use the shell (Terminal) to empty the Trash. It's dangerous and unnecessary, and it usually doesn't work.
A necessary system file is missing. If you know how that happened, restore it from a backup. Otherwise, see below.
If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.
If you use FileVault 2, then before running the Installer you must launch Disk Utility and select the icon of the FileVault startup volume ("Macintosh HD," unless you gave it a different name.) It will be nested below another icon with the same name. Click the Unlock button in the toolbar and enter your login password when prompted. Then quit Disk Utility to be returned to the main Recovery screen.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.
*The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

Getting error with sudo configuration on solaris 10

Valuable Member,
I have some issue with Sudo configuration on Solaris 10 (Sparc), I installed gcc & libiconv then install sudo package everything done well till I run "./configure" but when I run "make" its giving lots of error ... I am confused what I have to do ... Please tell me what exactly I have to do or what I am missing
---------------------------ERROR CUT-------------------------------------
# make
gcc -c -I. -I. -I/tmp/rsa -O2 -D__EXTENSIONS__ -D_PATH_SUDOERS=\"/etc/sudoers\" -D_PATH_SUDOERS_TMP=\"/etc/sudoers.tmp\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440 check.c
In file included from /usr/include/sys/wait.h:24,
from /usr/include/stdlib.h:22,
from check.c:31:
/usr/include/sys/siginfo.h:259: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:292: error: parse error before '}' token
/usr/include/sys/siginfo.h:294: error: parse error before '}' token
/usr/include/sys/siginfo.h:390: error: parse error before "ctid_t"
/usr/include/sys/siginfo.h:392: error: conflicting types for `__proc'
/usr/include/sys/siginfo.h:261: error: previous declaration of `__proc'
/usr/include/sys/siginfo.h:398: error: conflicting types for `__fault'
/usr/include/sys/siginfo.h:267: error: previous declaration of `__fault'
/usr/include/sys/siginfo.h:404: error: conflicting types for `__file'
/usr/include/sys/siginfo.h:273: error: previous declaration of `__file'
/usr/include/sys/siginfo.h:420: error: conflicting types for `__prof'
/usr/include/sys/siginfo.h:287: error: previous declaration of `__prof'
/usr/include/sys/siginfo.h:424: error: conflicting types for `__rctl'
/usr/include/sys/siginfo.h:291: error: previous declaration of `__rctl'
/usr/include/sys/siginfo.h:426: error: parse error before '}' token
/usr/include/sys/siginfo.h:428: error: parse error before '}' token
/usr/include/sys/siginfo.h:432: error: parse error before "k_siginfo_t"
/usr/include/sys/siginfo.h:437: error: parse error before '}' token
In file included from /usr/include/sys/procset.h:24,
from /usr/include/sys/wait.h:25,
from /usr/include/stdlib.h:22,
from check.c:31:
/usr/include/sys/signal.h:85: error: parse error before "siginfo_t"
In file included from /usr/include/stdlib.h:22,
from check.c:31:
/usr/include/sys/wait.h:86: error: parse error before "siginfo_t"
In file included from check.c:55:
/usr/include/signal.h:111: error: parse error before "siginfo_t"
/usr/include/signal.h:113: error: parse error before "siginfo_t"
*** Error code 1
make: Fatal error: Command failed for target `check.o'
---------------------END ERROR---------------------------
///Thanks
Mohammed Tanvir

How did you install gcc, I don't think its working correctly.
There should be a copy of gcc installed with solaris 10 in /usr/sfw/bin.
I suggest you use that one instead..

Authentication error with sudo

Hi there. I just tried using Carbon Copy Cloner (2.3) to clone my HD before updating to OS 10.4.9. I got this error: authentication error: sudo: /private/etc/sudoers is zero length
I booted to my old cloned drive and repaired permissions and the hard drive with my system on it. I also created a new user with admin privileges and tried it, and got the same error. I don't think it's a CCC-specific error because I got the same error when I tried to use Preferential Treatment to check for corrupt preferences.
Can anyone tell me how I might go about fixing this? I'm a longtime Mac user but don't know too much about Terminal and its uses. Help?
G5 dual 2.0 Mac OS X (10.4.7) 2.5G RAM, Radeon X800 XT video card

Thank you for looking, but I solved the problem by copying the sudoers file from my cloned drive back to my main drive. It was invisible, but File Buddy solved that problem.

Error with command "sudo: /etc/sudoers is mode 0777, should be 0440 Segmentation fault"

Similar Messages

Maybe you are looking for