Perforce: Difference between revisions
Jump to navigation
Jump to search
Created page with "#p4 admin stop #p4 verify -q //... #p4 admin checkpoint #use app "LaunchControl" to unload p4d global daemon #delete db.* files #upgrade p4 & p4d #p4d -jr checkpoint.xx <-- fi..." |
No edit summary |
||
| Line 1: | Line 1: | ||
==How to do a checkpoint and / or update perforce server to latest== | |||
#p4 admin stop | #p4 admin stop | ||
#p4 verify -q //... | #p4 verify -q //... | ||
| Line 12: | Line 14: | ||
#p4 verify -q //... | #p4 verify -q //... | ||
#p4 admin restart | #p4 admin restart | ||
==Using [http://www.soma-zone.com/LaunchControl/ LaunchControl] to manage the p4 server daemon== | |||
import [https://karaoke.kjams.com/resources/launch_control/perforce_launchcontrol.xml this file] into LaunchControl as a Global Daemon, ensure it's running. | |||
It should look like this:<br> | |||
https://karaoke.kjams.com/resources/launch_control/perforce_launch_control.png | |||
Revision as of 02:41, 6 November 2018
How to do a checkpoint and / or update perforce server to latest
- p4 admin stop
- p4 verify -q //...
- p4 admin checkpoint
- use app "LaunchControl" to unload p4d global daemon
- delete db.* files
- upgrade p4 & p4d
- p4d -jr checkpoint.xx <-- fill in number
- ensure the journal file has write access
- p4d -J journal -xu
- start / load p4d
- p4 counter lastCheckpointAction
- p4 verify -q //...
- p4 admin restart
Using LaunchControl to manage the p4 server daemon
import this file into LaunchControl as a Global Daemon, ensure it's running.
It should look like this:
