Exit Error 99
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of exit code 99 sccm this site About Us Learn more about Stack Overflow the company Business exit 99 band Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question linux exit code _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's eaddrnotavail how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top What does exit 99 means? up vote 4 down vote favorite I'm new to Unix. Just want to know what is exit 99 and why would one use it and what are the significance uses of it. For example, I'm using exit 99.
Unix Exit Codes
shell exit share|improve this question edited Apr 17 '14 at 23:40 Gilles 371k696751126 asked Apr 17 '14 at 7:43 Java_Alert 13514 I knew I loved you at exit 99. –Nick T Apr 17 '14 at 16:32 Pretty much similar answer to SO: "Why return a negative errno? (e.g. return -EIO)" –smci Apr 18 '14 at 6:51 add a comment| 5 Answers 5 active oldest votes up vote 22 down vote accepted There is no significance to exiting with code 99, other than there is perhaps in the context of a specific program. Either way, exit exits the shell with a certain exit code, in this case, 99. You can find more information in help exit: exit: exit [n] Exit the shell. Exits the shell with a status of N. If N is omitted, the exit status is that of the last command executed. share|improve this answer answered Apr 17 '14 at 7:46 Chris Down 55.7k7132166 2 Hey Thanks for the info!! –Java_Alert Apr 17 '14 at 8:08 4 Not quite - 99 is not zero, and so indicates that the program failed for some reason. &nda
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact
Linux Exit Codes
Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: bash exit codes Veritas Veritas PartnerNet STATUS CODE: 99 "NDMP backup failure" occurs when backing up a NDMP client. Article:000028907 Publish: Article URL:http://www.veritas.com/docs/000028907 Support return code / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set http://unix.stackexchange.com/questions/125179/what-does-exit-99-means up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 99 "NDMP backup failure" occurs when backing up a NDMP client. Error Message NDMP backup failure (99) Solution Overview:When backing up a NDMP server, it is possible for a status code 99 (NDMP backup failure) to occur. This error can occur in any of https://www.veritas.com/support/en_US/article.TECH37502 the following scenarios: None of the paths in the Network Data Management Protocol (NDMP) policy file list were backed up successfully. None of the backup paths exist on the NDMP host. An Incremental backup is run, but no files have changed since the last backup.The /etc/hosts file on a UNIX client contains an invalid localhost entry This error message has been reported on a variety of operating systems and NetBackup versions. This is not specific to any operating system or NetBackup version and could occur in other configurations.Troubleshooting:Check the NetBackup (tm) All Log Entries report for more information. For NetBackup 6.0 systems, check the logs for the ndmpagent originator ID for the server that is being created. Log Files:For NetBackup 6.0 systems, the unified logs for ndmpagent originator id 134 may list the following errors at the time the backup failure occurred. In this example, localhost (127.0.0.1) is being used as the name of the NDMP server. This was caused by having the NDMP server name appear for the localhost entry in the /etc/hosts file of the system.# vxlogview -o 134 -b "10/17/2006 12:07:38 AM"10/17/2006 12:07:38.263 [NdmpMoverSideShm::CreateServer] Creating server for 127.0.0.1 in Server Port Window 1025 to 5000 10/17/2006 12:07:38.271 [NdmpMoverSideShm::CreateServer] M
4 UNIX_LINUX_INSTALL ITM_UNIX_INSTALL ITM_LINUX_INSTALL GSKit installation installs failure Technote (troubleshooting) Problem(Abstract) Installation on UNIX/Linux http://www-01.ibm.com/support/docview.wss?uid=swg21377580 uses install.sh; running this fails with a "runGSkit failure: Return error code: 99" and a "install.sh failure: Return error code: 4". Symptom The full sample output looks like https://www.npmjs.com/package/grunt-fail this: runGSkit failure: Return error code: 99. runGSkit failure: GSKit check failure, script: /opt/IBM/ITM/ls3263/gs/bin/private_verifyinstall. runGSkit failure: ls3263 - GSK check error, verifyInstall test failed. install.sh failure: Return exit code error code: 4. Diagnosing the problem Since it failed within runGSkit when it called verifyInstall, review the CH/logs/candle_installation.log file and look for references to runGSkit. For example, output similar to the following might be present: runGSkit: ----- Running command: /opt/IBM/ITM/ls3263/gs/bin/private_verifyinstall ----- /opt/IBM/ITM/ls3263/gs/bin/gsk7ver: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No linux exit code such file or directory Error: Verify Failed Expected Details of gskit in /opt/IBM/ITM/ls3263/gs Got runGSkit: return code from command is 99 runGSkit: ----- End of running command ----- runGSkit: error Return error code: 99 runGSkit: error GSKit check failure, script: /opt/IBM/ITM/ls3263/gs/bin/private_verifyinstall runGSkit: error ls3263 - GSK check error, verifyInstall test failed Resolving the problem In the example above, which is for Linux running on z/OS (zLinux), the libstdc++.so.5 file was not present in the library path. On zLinux, this file comes from the package compat-libstdc++-33-3.2.3-61.s390.rpm. When this package was installed, the problem no longer occurred. For other platforms, the corresponding architecture-specific package would need to be installed (compat-libstdc++-33-3.2.3-61.x86_64.rpm and compat-libstdc++-33-3.2.3-61.i386.rpm). Document information More support for: Tivoli Components ITM Distributed Installer V6 Software version: All Versions Operating system(s): AIX, Linux, Solaris Reference #: 1377580 Modified date: 2009-03-23 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
an error message and exit code of choice. Installation Change directories to the root directory of your project npm install grunt-fail Add the following line to your Gruntfile.js grunt.loadNpmTasks('grunt-fail'); Usage The simplest usage is without any arguments, e.g. grunt fail from the command line or grunt-fail takes an optional error message and an optional exit code as arguments. For example grunt "fail:Don't deploy:26" If there is just one argument, it can be either a numerical exit code, or an error message. The default message is "Failed on purpose." The default exit code is 255. More examples grunt fail:6 grunt "fail:no thanks" You can use it in an alias task like this task('test', ['vows', 'fail:99']); Exit codes Grunt seems to do best across platforms with exit codes between 1 and 255 inclusive. Negative numbers might work, but it adds them to 256 to make them positive on some platforms. Grunt doesn't consider an exit code of zero an error, so it won't fail. Don't use it! Here are the exit codes used by grunt for reference. Bugs, etc. Please report any bugs, feature requests, etc. to grunt-fail's github issue tracker. Private packages for the whole team It’s never been easier to manage developer teams with varying permissions and multiple projects. Learn more about Private Packages and Organizations… how? learn more adamstallard published 2013-05-25T06:13:09.412Z 0.3.2 is the latest of 6 releases github.com/goalzen/grunt-fail MIT ® Collaborators Stats 3 downloads in the last day 33 downloads in the last week 133 downloads in the last month Have an issue? File it. on GitHub on GitHub Try it out Test grunt-fail in your browser. Keywords deploy, exit, return, error, fail, build, deployment, grunt, grunt