p4 Perforce server on Mac OS X 10.4 Zoltan Grose Wed May 30 00:14:30 PDT 2007. Previous message:. Next message:. Messages sorted by: I use p4d on my Mac.
But I just fire up p4d manually. Only a 3 user license here. Just a couple comments.
P4V (com.perforce.p4v) is a Mac software application that has been discovered and submitted by users of Aploader. Install Git on Mac OS X Install Git on Windows Install Git on Linux. Git Cheatsheet. Getting Started. Perforce to Git - why to make the move. Perforce, for the most part, requires a connection to the server in order to even see the history of changes. And that single central server becomes a bottleneck as teams and projects get bigger.
Mac OS X is a gorgeous system, but there are a few strikes against it:. Linux is cheaper and is more server oriented. Clearly only a benefit in the headless server environment. I want my workstation to be user oriented! =). People are more familiar with Linux and Solaris.
Most 3rd party products are Linux oriented and not Mac oriented Actually, that's usually a strike against the 3rd party products in my book since those same tools usually are a complete PITA to learn and use. Heck, Linux is a PITA to learn and use! Any case, no place for a platform war, just wanted to chime in on those points. If you ever get around to step-by-step instructions for setting up p4d, let us know. I'll QA your steps on my system.z On May 29, 2007, at 8:21 PM, Dave Lewis wrote: sorry about the blank email. anyway, I'd be interested in the mac guide. I started p4d on my macbut the startup stuff was so different than unix that I put it off.
I'l love to know the in and out of setting it up to startup on boot. one of the things I really like now about the mac is having all those unix utils right there. It even came with emacs and perl installed! dave On 5/29/07, Qazwart wrote: On May 29, 2007, at 9:44 PM, Paquet, Philippe wrote: To clarify, I had to fix the ownership of p4d as a file but I'm running p4d with a non-privileged user that doesn't even has shell access. That's the way to go.
I'm using tiger (Mac OS 10.4), so I wrote a plist for launchd. Startup Items are still supported but they have been deprecated. Startup Items have been deprecated? I guess I better learn the newer method of starups.
I'm surprised to see so few peoples running p4d on Mac OS X as it's pretty much FreeBSD with a nice graphic interface on the top. It's very stable and very lean in term of resources. Mac OS X is a gorgeous system, but there are a few strikes against it:. Linux is cheaper and is more server oriented.
People are more familiar with Linux and Solaris. Most 3rd party products are Linux oriented and not Mac oriented. Macs aren't 100% like other Unix systems in their configuration. For example, the startup setup is completely different from other Unix-like systems.
It's not that Macs are worse than other Unix systems to configure. Just different which means you've got to learn another way to do things. Apple hasn't yet pushed Macs for business systems. I bet that will change with the next release when Mac OS X will be stabilized enough for businesses to consider. Licensing is a major problem. Windows and Linux aren't limited to a particular hardware vendor.
If Mac OS X Server was permitted to run on any PC, it would be a lot more popular. However, the hardware and software restrictions will continue to limit the Mac's push into the server/business arena. Do you think a step by step guide will be of interest to anyone or will I be wasting my time? I'm going to be writing an article for TidBITs about version control on the Mac and why you should use version control, so it would actually be quite handy.
In fact, it may become a handy guide for Mac users who aren't using Perforce since what you learned about getting p4d up and running on a Mac would also apply to Subversion, or any other client/server program that you want to run at startup. -Original Message- From: Qazwart mailto: Sent: Tuesday, May 29, 2007 6:19 PM To: Paquet, Philippe Cc: Subject: Re: p4 Perforce server on Mac OS X 10.4 I originally ran p4d on my home Mac, but I ended up switching to Subversion for home use. Subversion has terrible merging capabilities and doesn't have a decent GUI front-end, but for personal projectsmerging isn't an issue and my favorite IDE is 'vi'. The big advantage with Subversion for me is the ability to have dozens of workspaces (one for each project) without worrying about licensing limitations.
Perforce Mac Environment Variables
That probably makes you a rare bird to run p4d on a Mac. Most people either run p4d on Linux, Unix, or if they are unlucky, on Windows. Macs are not big commercial machines, and the infrastructure to support a server side Mac is limited. However, I do run the Perforce client on my Mac when I use the Perforce public depot. By the way, you shouldn't be running 'p4d' as root or any wheel user because of security concerns.
Imagine if someone found a way to get p4d to execute their code. If p4d ran as a privileged user, it would be able to run that code as 'root'. You need to run p4d as a standard, unprivileged user and make sure all the database filesdepot files, and triggers are owned by that user.
Of course, the problem is how do you start p4d as a user when you have 'root' starting up all the processes. That's where the 'su' program comes in. It allows you to run a program as another user. You might also look at this article: pub/ a/mac/2003/10/21/startup.html which tells you how to make a startup item.
Startup items on the Mac are a bit different from the way it works on many other Unix systems, so it's worth taking a look at it. On May 29, 2007, at 7:53 PM, Paquet, Philippe wrote: I resolved the problem on Sunday. I actually had 2 different problems: - p4d was owned by the unprivileged user, not root:wheel - The volume that is hosting the journal was mounted later in the boot process. So, p4d was not able to open the journal.
I'll try to write a web page with step by step instructions and an example plist file. It's not as obvious as it should be. Thanks a lot David:) Are we the only guys running p4d on Mac OS X?
-Original Message- From: David Weintraub mailto: Sent: Monday, May 28, 2007 5:03 PM To: Paquet, Philippe Cc: Subject: Re: p4 Perforce server on Mac OS X 10.4 Okay, so p4d works and goes into daemon mode on the command line. The next step is to check the 'Console' application (usually under /Applications/Utilities) and see if p4d is reporting any error message. That might give you a hint why it quits. For example, it might not have the correct 'P4ROOT' defined, or it could be starting up as the wrong user.
You have to start it up as the user who owns 'P4ROOT' and not as 'root'. A good way to start p4d as the correct user is to use it as an argument to the 'su' command: su - -c '$P4Duser -dr $P4ROOT' When part of the startup sequence, p4d is started as user 'p4AdminUser'. On 5/25/07, Paquet, Philippe wrote: That works.
Perforce Mac Hostname
The problem I have is to get the perforce server to start automatically when the machine start as an unprivileged user. I created a plist for that but when the launch daemon runs it, p4d quit straight away. -Original Message- From: David Weintraub mailto: Sent: Friday, May 25, 2007 9:35 AM To: Paquet, Philippe Cc: Subject: Re: p4 Perforce server on Mac OS X 10.4 Can you start up the server by doing a 'p4d -d' command from the command line while logged in as the Perforce depot owner (and not as root)? I have Mac OS X 10.4 and I am able to do that. On 5/24/07, Paquet, Philippe wrote: Hi GuysDoes anyone has experience installing a Perforce server on Mac OS X 10.4?
I'm having trouble running it as a daemon using a non privileged user. ThanksPhilippe - - - - - Vivendi Games-: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material of Vivendi Games which is for the exclusive use of the individual designated above as the recipient. Any review, retransmissiondissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact immediately the sender by returning e-mail and delete the material from any computer. If you are not the specified recipient, you are hereby notified that all disclosurereproduction, distribution or action taken on the basis of this message is prohibited.