Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Letterman]

Hi,
everytime I'm using aMule 2.1.0, the Mac Mini doesn't boot on the next restart.
I have to boot from cd and have to repair the permissions.
Before aMule can start, I have to set up the hostname with the admin password.
The last few days, I didn't use aMule and the System booted correctly.
Yesterday I tested again and started aMule (Tiger edition on Tiger).
Logout and login worked fine, but at the reboot, Tiger couldn't start
without boot it from cd and repair the file permissions.

[ken]

That's very strange.  aMule doesn't have any privileges beyond those that a normal user process has.  So, it shouldn't be able to modify any permissions for system directories.  Especially those necessary for booting.

What files have broken permissions?  I'm certain that aMule is not intentionally changing the permissions of any files other than the ones it downloads and creates.

Are you running as an Admin user?  That's generally not recommended.  If aMule is doing something that it shouldn't be, the damage would be more limited if you were running as a non-Admin user.  If you're already non-Admin then that makes it even less likely that aMule could change the permissions of system files.

You might check your disk for corruption.  While aMule doesn't change the permissions of files, it does stress the file system (and disk) far more than most applications.  If the disk has corruption, then aMule's heavy use could cause that corruption to spread to system-critical places (without regard to file permissions).

[Letterman]

Hi,
the disk isn't corrupted.
I'm usind the admin account, but unlike the root account at linux,
the use of the admin account at osx isn't dangerous.
Now I changed the account to standard. Let's see.
I don't know which permissions really are corrupted,
because some values changed between 10.4.2 (DVD) and 10.4.5.

Die Zugriffsrechte für „./usr/lib/php/build/Makefile.global“ unterscheiden sich, Soll-Wert „-r--r--r-- “, Ist-Wert „-r-xr-xr-x “
Eigentümer und Gruppe wurden für „./usr/lib/php/build/Makefile.global“ korrigiert
Zugriffsrechte wurden für „./usr/lib/php/build/Makefile.global“ korrigiert


Die Zugriffsrechte für „./usr/lib/php/build/acinclude.m4“ unterscheiden sich, Soll-Wert „-r--r--r-- “, Ist-Wert „-r-xr-xr-x “
Eigentümer und Gruppe wurden für „./usr/lib/php/build/acinclude.m4“ korrigiert
Zugriffsrechte wurden für „./usr/lib/php/build/acinclude.m4“ korrigiert


Die Zugriffsrechte für „./usr/lib/php/build/mkdep.awk“ unterscheiden sich, Soll-Wert „-r--r--r-- “, Ist-Wert „-r-xr-xr-x “
Eigentümer und Gruppe wurden für „./usr/lib/php/build/mkdep.awk“ korrigiert
Zugriffsrechte wurden für „./usr/lib/php/build/mkdep.awk“ korrigiert


Die Zugriffsrechte für „./usr/lib/php/build/phpize.m4“ unterscheiden sich, Soll-Wert „-r--r--r-- “, Ist-Wert „-r-xr-xr-x “
Eigentümer und Gruppe wurden für „./usr/lib/php/build/phpize.m4“ korrigiert
Zugriffsrechte wurden für „./usr/lib/php/build/phpize.m4“ korrigiert


Die Zugriffsrechte für „./usr/lib/php/build/scan_makefile_in.awk“ unterscheiden sich, Soll-Wert „-r--r--r-- “, Ist-Wert „-r-xr-xr-x “
Eigentümer und Gruppe wurden für „./usr/lib/php/build/scan_makefile_in.awk“ korrigiert
Zugriffsrechte wurden für „./usr/lib/php/build/scan_makefile_in.awk“ korrigiert

[bootstrap]

Hi there,

I'm usind the admin account, but unlike the root account at linux,
the use of the admin account at osx isn't dangerous.

You're right that OS X has some nice security related features, but that doesn't make it failsafe. I still wouldn't advise to run amule as a privileged user, whaterver os you run.

Regarding to the files you listed in your last post i'm quite sure that:
* amule has nothing to do with that
* none of those changed permissions should prevent your system from booting

Can you provide more detail on what changes on your system that prevents it from booting correctly?

You really should create some kind of "normal" user on your system and run amule as that user. Make sure the user has the necessary permissions to write into amules files/folders and nothing more. That way you can be sure that amule can't modify any important file on your system, which it normally - as far as i can say - does not.

Cheers,
boot

[Letterman]

If the system wants to start, it shows an empty grey screen.
After some time it flashes the finder icon and a "?",
what shows me, that OSX can't find the system.

If I repair the permissions, the system boots normally.
Very strange.
Now I have a normal user account and I'll check it out when I got the time.

[lionel77]

Very weird.

First, those php files with messed up permissions are owned by user 'system' & group 'wheel'. That means that you as a non-root user and programs that you are running are not capable of changing those permissions unless you escalate your privileges via sudo, which would require you to enter your password.

Second, the grey screen with the flashing '?' indicates that your system can't find a bootable volume, which is pretty serious and could imho not result from messed up permissions. My intuition is (as ken has suggested) that there is something wrong with your hard drive and aMule makes this problem more obvious, because it puts more stress on your drive. If it happens again, you could try to boot from your DVD and just do a "Repair Disk" but no "Repair Permissions" from within Disk Utility. My intuition is that that would allow you to boot from the disk again, too.

While Apple's Disk Utility is ok for checking and repairing disks, there are better utilities like DiskWarrior and TechTool Pro. Maybe you know somebody who has one of these apps, so you could take it on a test drive.