Non pas cmd-shift, mais juste shift
Oups, merci Remy d'avoir corrigé
Non pas cmd-shift, mais juste shift
Bonne idée.Petite interrogation : n'est-ce pas un des symptômes que l'on peut rencontrer avec un disque dur saturé ?
-usurp-
process 1 exec of /sbin/launch failed...
BSD process name corresponding to current thread: init
-bash-3.2# df -H
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/disk1s2 1.3G 1.2G 111M 92% 286329 27028 91% /
devfs 197k 197k 0B 100% 666 0 100% /dev
/dev/disk2 524k 147k 377k 29% 34 92 27% /Volumes
/dev/disk3 524k 143k 381k 28% 33 93 26% /private/var/tmp
/dev/disk4 524k 156k 369k 30% 36 90 29% /private/var/run
/dev/disk5 524k 147k 377k 29% 34 92 27% /System/Installation
/dev/disk6 524k 266k 258k 51% 63 63 50% /private/var/db
/dev/disk7 6.3M 1.7M 4.5M 28% 424 1110 28% /private/var/folders
/dev/disk8 2.1M 233k 1.9M 12% 55 455 11% /private/var/root/Library
/dev/disk9 1.0M 152k 897k 15% 35 219 14% /Library/ColorSync/Profiles/Displays
/dev/disk10 524k 172k 352k 33% 40 86 32% /Library/Preferences
/dev/disk11 524k 160k 365k 31% 37 89 29% /Library/Preferences/SystemConfiguration
/dev/disk12 1.0M 143k 905k 14% 33 221 13% /Library/Keychains
/dev/disk0s2 249G 78G 171G 32% 19124569 41715173 31% /Volumes/Mac
/dev/disk0s3 650M 496M 147M 78% 122681 36009 77% /Volumes/Image Volume
-bash-3.2#