Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

Debugging a Mac OS X Installer

deployexpert created the topic: Debugging a Mac OS X Installer
InstallAnywhere utilizes the standard output layers in Mac OS X to display output. To
gather debugging output from an OS X installer, launch Console.app found in /
Applications/Utilities. To retain this information, cut and paste information from the
console window to a file.
If you do not see debug output from an installer, check the Info.plist file inside the
installer. To do this, Control-click (or right click) on the installer and select Show
Package Contents. Inside the Contents folder you will see an XML file named
Info.plist. You’ll need to change:
lax.stderr.redirect

lax.stdout.redirect

to
lax.stderr.redirect
console
lax.stdout.redirect
console
When you relaunch the installer, the installer output should be now listed in
Console.app.

Rajesh Kumar
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x