Desinstalar programas PKG
- Autor Videl
- Fecha de inicio
- Estado
senhez
Applesan@
miliuco
Nuev@ Applesan@
Videl, a mano se pueden eliminar bastantes programas teniendo en cuenta que hay que buscar carpetas o archivos con el nombre del programa en:
~/Library
~/Library/Preferences
~/Library/Application support
/Library/Preferences
Applications
En las carpetas Preferences (del usuario y del sistema) suelen estar los archivos PLIST de configuración en formato XML, suelen llamarse
com.apple.nombre-del-programa.plist
com.nombre-del-fabricante.nombre-del-Programa.plist
~/Library
~/Library/Preferences
~/Library/Application support
/Library/Preferences
Applications
En las carpetas Preferences (del usuario y del sistema) suelen estar los archivos PLIST de configuración en formato XML, suelen llamarse
com.apple.nombre-del-programa.plist
com.nombre-del-fabricante.nombre-del-Programa.plist
juker12
Nuev@ Applesan@
Videl que no te quite el sueño eso. mac OS X se basa en unix, y unix posee una potente utilidad llamada cron. Este se encarga periodicamente de limpiar segun su criterio interno, por _ por & ect.
( es un programador de tareas estandar, entre ellas la de borrar archivos y carpetas huerfanas)
Aunque es verdad, que a veces nos quieren meter utilidades de este tipo como si os x fuera un windows.
mas info de cron y sintaxis.
BSD System Manager's Manual
cron -- daemon to execute scheduled commands (Vixie Cron)
cron [-s] [-o] [-x debugflag[,...]]
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in
/usr/lib/cron/tabs. There should be no need to start it manually. See
/System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in
/etc/passwd; crontabs found are loaded into memory. The cron utility also searches for /etc/crontab
which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to
see if it should be run in the current minute. When executing commands, any output is mailed to the
owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if such
exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modifi-cation modification
cation time on /etc/crontab) has changed, and if it has, cron will then examine the modification time
on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a
crontab file is modified. Note that the crontab(1) command updates the modification time of the spool
directory whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such
as the switches between the standard time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a
time interval that disappears (for example, during the switch from standard time) to daylight
saving time or is duplicated (for example, during the reverse switch), then it is handled in
one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the
disappearing or duplicated interval. In other words, if the job had run within one hour before
the GMT offset change (and cron was not restarted nor the crontab(5) changed after that) or
would run after the change at the next hour. They work as always, skip the skipped time or run
in the added time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they
are not skipped nor executed twice (unless cron is restarted or the user's crontab(5) is
changed during such a time interval). If an interval disappears due to the GMT offset change,
such jobs are executed at the same absolute point of time as they would be in the old time
zone. For example, if exactly one hour disappears, this point would be during the next hour at
the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes,
to be compatible with the old (default) behavior. If both options -o and -s are specified, the
option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma
separated debugflag identifiers must be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
( es un programador de tareas estandar, entre ellas la de borrar archivos y carpetas huerfanas)
Aunque es verdad, que a veces nos quieren meter utilidades de este tipo como si os x fuera un windows.
mas info de cron y sintaxis.
BSD System Manager's Manual
cron -- daemon to execute scheduled commands (Vixie Cron)
cron [-s] [-o] [-x debugflag[,...]]
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in
/usr/lib/cron/tabs. There should be no need to start it manually. See
/System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in
/etc/passwd; crontabs found are loaded into memory. The cron utility also searches for /etc/crontab
which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to
see if it should be run in the current minute. When executing commands, any output is mailed to the
owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if such
exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modifi-cation modification
cation time on /etc/crontab) has changed, and if it has, cron will then examine the modification time
on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a
crontab file is modified. Note that the crontab(1) command updates the modification time of the spool
directory whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such
as the switches between the standard time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a
time interval that disappears (for example, during the switch from standard time) to daylight
saving time or is duplicated (for example, during the reverse switch), then it is handled in
one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the
disappearing or duplicated interval. In other words, if the job had run within one hour before
the GMT offset change (and cron was not restarted nor the crontab(5) changed after that) or
would run after the change at the next hour. They work as always, skip the skipped time or run
in the added time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they
are not skipped nor executed twice (unless cron is restarted or the user's crontab(5) is
changed during such a time interval). If an interval disappears due to the GMT offset change,
such jobs are executed at the same absolute point of time as they would be in the old time
zone. For example, if exactly one hour disappears, this point would be during the next hour at
the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes,
to be compatible with the old (default) behavior. If both options -o and -s are specified, the
option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma
separated debugflag identifiers must be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
Videl
Nuev@ Applesan@
miliuco
Nuev@ Applesan@
El Aprendiz
Nuev@ Applesan@
miliuco
Nuev@ Applesan@
juker12
Nuev@ Applesan@
Encontre una utilidad en modo grafico para cron
Programas la tarea limpiar x carpetas cada X tiempo, y te olvidas para los restos.
Mac OS X Remove Localized Files: Mac OS X and many Mac OS X applications include files that allow them to be used by people who speak different languages. Even if you choose not to install "extra" languages, your Mac usually has several alternate languages available. And every time you install or update an application, you get more of them. For example, the iTunes 4.0 installer includes Chinese (both Taiwan and mainland), Danish, Dutch, English, Finnish, French, German, Italian, Korean, Japanese, Norwegian, Portuguese, Spanish, and Swedish versions.
If you don't speak some of those languages, you'll never use those files (and never miss them), so you can safely remove them and save disk space. There are other applications that can do this, but to be really useful you'll need to run them again every time you install a new application or update Mac OS X.
These files can take more space than you might guess. The first time I ran this job on my Mac, I saved 322MB of files I was never going to use anyway. With that space I could import a half-dozen of my CDs into iTunes and not be using any more disk space than when I started.
Removing localized files can take a while, mostly taken up in looking for the files, and will take longer on larger drives. For reference it akes about 10-12 minutes on a drive with about 22GB used. This job requires that you configure it, so that you can tell it which languages you want to remove.
Una carpeta a mirar esta en library/receipts que alli guarda todos los repositorios de *.pkg y suele ocupar mucho
Programas la tarea limpiar x carpetas cada X tiempo, y te olvidas para los restos.
Mac OS X Remove Localized Files: Mac OS X and many Mac OS X applications include files that allow them to be used by people who speak different languages. Even if you choose not to install "extra" languages, your Mac usually has several alternate languages available. And every time you install or update an application, you get more of them. For example, the iTunes 4.0 installer includes Chinese (both Taiwan and mainland), Danish, Dutch, English, Finnish, French, German, Italian, Korean, Japanese, Norwegian, Portuguese, Spanish, and Swedish versions.
If you don't speak some of those languages, you'll never use those files (and never miss them), so you can safely remove them and save disk space. There are other applications that can do this, but to be really useful you'll need to run them again every time you install a new application or update Mac OS X.
These files can take more space than you might guess. The first time I ran this job on my Mac, I saved 322MB of files I was never going to use anyway. With that space I could import a half-dozen of my CDs into iTunes and not be using any more disk space than when I started.
Removing localized files can take a while, mostly taken up in looking for the files, and will take longer on larger drives. For reference it akes about 10-12 minutes on a drive with about 22GB used. This job requires that you configure it, so that you can tell it which languages you want to remove.
Una carpeta a mirar esta en library/receipts que alli guarda todos los repositorios de *.pkg y suele ocupar mucho
El Aprendiz
Nuev@ Applesan@
- Estado
