On 11/05/11 17:16, John Dennis wrote:

On 05/11/2011 12:04 PM, Gary Gatten wrote:

...

Good morning,

I’m wanting to upgrade to 2.1.10, however, I want to install **all** files to a different location so I don’t overwrite **any** 2.1.6 production files. Once I’ve validated operation on 2.1.10 I’ll install it to it’s normal location.

So, if I specify –prefix=/devel/; will this work OK for what I’m wanting – or do I need to take other actions as well, such as: --with-radacctdir= and --with-raddbdir=, etc.?

The preferred mechanism is to specify DESTDIR, every installed file/directory is then created in it's "normal" location, but hung under a DESTDIR root. You can either:

That's fine for packaging, but if you actually want to *run* the server from /devel, ./configure --prefix=/devel is surely preferred, as it'll update the include paths in the generated config & dictionaries.

Thanks for the prompt reply! I'm actually running RHEL. I couldn't find where "DESTDIR" would be referenced, nor that "R=" is a valid argument. Are these 'undocumented' options? I guess I can try it and see what happens! G -----Original Message----- From: John Dennis [mailto:jdennis@redhat.com] Sent: Wednesday, May 11, 2011 11:16 AM To: FreeRadius users mailing list Cc: Gary Gatten Subject: Re: Install new version (2.1.10) to completely different location On 05/11/2011 12:04 PM, Gary Gatten wrote:

Good morning,

I'm wanting to upgrade to 2.1.10, however, I want to install **all** files to a different location so I don't overwrite **any** 2.1.6 production files. Once I've validated operation on 2.1.10 I'll install it to it's normal location.

So, if I specify -prefix=/devel/; will this work OK for what I'm wanting - or do I need to take other actions as well, such as: --with-radacctdir= and --with-raddbdir=, etc.?

The preferred mechanism is to specify DESTDIR, every installed file/directory is then created in it's "normal" location, but hung under a DESTDIR root. You can either: export DESTDIR=/devel or make install R=/devel -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/ <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>

I am only installing from source, I apologize if I lead you to believe otherwise. I've copied all known 216 dirs and files and have built/installed 2110 using --prefix and several other args to ensure all files were placed under /devel/. In some cases files were placed directly under /devel/ where I expected a child dir would be created, but that's fine for my purposes. And yes, I want to execute radiusd from the /devel directory. I have to tweak the clients file and such, bu should be ready to fire it up shortly. Thanks all for your help! G ----- Original Message ----- From: John Dennis [mailto:jdennis@redhat.com] Sent: Wednesday, May 11, 2011 11:54 AM To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Cc: Gary Gatten Subject: Re: Install new version (2.1.10) to completely different location On 05/11/2011 12:24 PM, Gary Gatten wrote:

Thanks for the prompt reply!

I'm actually running RHEL. I couldn't find where "DESTDIR" would be referenced, nor that "R=" is a valid argument. Are these 'undocumented' options?

I guess I can try it and see what happens!

You didn't say you were installing pre-built RPM's, that's a different matter altogether, I though you were building from source. You can't simultaneously install two different versions of the same RPM. Here are a few suggestions for your use case in order of preference: * Always keep your config files under source code control. That's a good idea for a variety of reasons. After you install a new version of freeradius from RPM you can tweak to your hearts desire, once all is good (or better yet incrementally) commit the files, you can always roll back versions at your discretion. Source code control is a good thing (tm). If the config is under source code control you'll always have history, you can tag working configurations, do experiments, etc. all without fear. * After an RPM install the new config files from the new version should appear as xxx.rpmnew if you've modified the previous verserion, where xxx is a config file. * copy /etc/raddb to a backup location. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/ <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>

Hi Alan, I did read that in the doc somewhere, but I didn't want to overwrite any files; bins, modules, confs, doc, etc. I wanted to be sure the prod 2.1.6 remains 100% unchanged when I install/test 2.1.10. So far so good! G ----- Original Message ----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: Wednesday, May 11, 2011 01:48 PM To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Install new version (2.1.10) to completely different location Gary Gatten wrote:

I’m wanting to upgrade to 2.1.10, however, I want to install **all** files to a different location so I don’t overwrite **any** 2.1.6 production files.

FreeRADIUS does *not* over-write any production configuration files. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>