Prebind/re-prebind?
1 - 4 of 4 Posts
Joined
·
3,309 Posts
Here is a very limited explanation form Xupport:
update prebinding
ensures that prebinding information is up-to-date after new prebound applications or new versions of system libraries are installed.
re-prebind
The force option ensures that all files examined are re-prebound, even if the prebinding is otherwise up-to-date. It will prebind all binaries on the volume, even if otherwise correct.
Make sense ?!?
Well it's a start...
![]()
update prebinding
ensures that prebinding information is up-to-date after new prebound applications or new versions of system libraries are installed.
re-prebind
The force option ensures that all files examined are re-prebound, even if the prebinding is otherwise up-to-date. It will prebind all binaries on the volume, even if otherwise correct.
Make sense ?!?
Well it's a start...
How about this...
Prebinding decides what system libraries are needed to run the application and that information is made known to the application.
(How it actually does it I haven't looked at)
When you install an application, at the end of the install there's that "Optimizing system" step, that's prebinding. So you don't normally need to go around a do a "sudo prebind"....
Help a little more?
John
Prebinding decides what system libraries are needed to run the application and that information is made known to the application.
(How it actually does it I haven't looked at)
When you install an application, at the end of the install there's that "Optimizing system" step, that's prebinding. So you don't normally need to go around a do a "sudo prebind"....
Help a little more?
John
Joined
·
778 Posts
Actually the prebinding runs periodically by the system on its own in the background.
If you open a terminal and go to the /var/log/ directory and open up the system.log or just run: tail -100 /var/log/system.log, you might be able to see the last time the system ran the prebinding update.
Basically Johnny G4 is right in that you do not normally need to go and run it yourself. If you notice the system slowing down you can always run it and then reboot.
The biggest files to worry about at the log files that get rotated and the locate db that gets rebuilt. These are run late at night (if you keep your comptuer on overnight) and run by crontab scripts. The biggest thing that these scripts actually do is backup the "local.nidb". This right now is the heart and soul of all your user and system information.
To run these yourself open a terminal and type:
sudo periodic daily weekly monthly
password:
give it a couple of minutes as it starts to run it's course and then you will be given a command prompt at the end and you can exit..
WOW, I got way off topic there. Sorry
If you open a terminal and go to the /var/log/ directory and open up the system.log or just run: tail -100 /var/log/system.log, you might be able to see the last time the system ran the prebinding update.
Basically Johnny G4 is right in that you do not normally need to go and run it yourself. If you notice the system slowing down you can always run it and then reboot.
The biggest files to worry about at the log files that get rotated and the locate db that gets rebuilt. These are run late at night (if you keep your comptuer on overnight) and run by crontab scripts. The biggest thing that these scripts actually do is backup the "local.nidb". This right now is the heart and soul of all your user and system information.
To run these yourself open a terminal and type:
sudo periodic daily weekly monthly
password:
give it a couple of minutes as it starts to run it's course and then you will be given a command prompt at the end and you can exit..
WOW, I got way off topic there. Sorry
1 - 4 of 4 Posts
Join the discussion
