Guru Of Geeks

Introduction A keytab is a file containing pairs of  Kerberos  principals and encrypted keys (which are derived from the Kerberos password). You can use a keytab file to authenticate to various remote systems using Kerberos without entering a password. However, when you change your Kerberos password, you will need to recreate all your keytabs. Keytab files are commonly used to allow scripts to automatically authenticate using Kerberos, without requiring human interaction or access to password stored in a plain-text file. The script is then able to use the acquired credentials to access files stored on a remote system. Creating a keytab file You can create keytab files on any computer that has a Kerberos client installed. Keytab files are not bound to the systems on which they were created; you can create a keytab file on one computer and copy it for use on other computers. Following is an example of the keytab file creation process using MIT Kerberos: > ktutil ktutil: addent -...

Even though we have enough space for all the director for IBM IIS, We do get the error message "error: No space left on device" Try to find if this is an inodes problem with: df -ih Try to find root folders with large inodes count: for i in /*; do echo $i; find $i |wc -l; done Try to find specific folders: for i in /src/*; do echo $i; find $i |wc -l; done To clear the &PH& directory from within DataStage: Ensure there are no DataStage jobs running anywhere on the system by running "ps -ef | grep DSD" From the DataStage Administrator, go to the Projects page, select the project whose file you want to clear and click the Command button. The Command Interface dialog box opens. Type the following into the command field: CLEAR.FILE &PH& (all uppercase) Click Execute to run the command and clear the file.

Issue: Failed building wheel for Pillow Running setup.py clean for Pillow Solution: sudo apt-get install python-dev sudo apt-get install libjpeg8-dev sudo ln -s /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib pip install pillow

Issue : Installing sentry Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-y2kyiV/psycopg2/ ​Solution:  ​ Python 2 sudo apt install libpq-dev python-dev Python 3 sudo apt install libpq-dev python3-dev ​

I installed postfix and got this error: postdrop: warning: unable to look up public/pickup: No such file or directory. Turns out that sendmail was previously installed and that was messing things up. I had to stop sendmail and make the appropriate directory and restart postfix. Specifically: mkfifo /var/spool/postfix/public/pickup ps aux | grep mail kill  sudo /etc/init.d/postfix restart Test emailing  #email youremail@abc.com (enter) subject: test (enter) test (ctrl+d) cc: youremail@abc.com (enter) if your receive above then email everything is fine now! :)

Question How do I create and use a value file within a parameter set in DataStage? Answer Using a value file in a parameter set allows you to set values of a parameter dynamically. For Example: Job A updates the value file. Job B uses a parameter set that points to that value file. When moving jobs from development to test or production you can update the value file to reflect different values for the different environments without having to recompile the job. To create a new Parameter Set, select File, New and select "Create new Parameter Set" This will Launch a Dialog shown below: Fill out the appropriate information on the General tab and the proceed to the Parameters Tab: In this tab, enter in the Parameters you wish to include in this Parameter Set. Note that you can also add existing Environmental Variables. The last tab, Values, allows you to specify a Value File name. This is the name of the file that will automatically be created on the Engine tier. This tab also all...

Problem(Abstract) A DataStage job does not use the new value that is put in the Parameter set. Cause If you make any changes to a parameter set object, these changes will be reflected in job designs that use this object up until the time the job is compiled. The parameters that a job is compiled with are the ones that will be available when the job is run (although if you change the design after compilation the job will once again link to the current version of the parameter set). Diagnosing the problem Examine the log entry "Environment variable settings" for parameter sets. If the parameter set specifies the value "(As predefined)", the parameter set is using the value that was used during the last compile. Resolving the problem If the value of the parameter set may be changed, you should specify a Value File for the parameters or set the parameters in the parameter set (including encrypted parameters) to $PROJDEF. ​​