02-01-2013
Quote:
Originally Posted by
scriptor
hi RudicC
is it necessary to use environmental variable in case of IFS .
why we are this
is IFS is itself a environmental variable ? i think it is not but i am not sure
When a shell starts, the IFS variable may be inherited from the environment or initialized by the shell to <space>, <tab>, and <newline> in that order. If IFS is unset (which is very different from setting IFS to an empty string), the shell and the read speical built-in utility split fields as if IFS had been set to <space>, <tab>, and <newline> in that order.
When you need to use non-default word splitting (e.g., using : as the field separator when grabbing directories out of $PATH), saving the old value and restoring it after you have completed the need for special word splitting actions is just good programming practice. In the example code given, OLDIFS is used to save the old value of IFS before setting IFS to
:. After $PATH is split, setting IFS to OLDIFS restores its original value (as long as it hadn't been unset).
Whether or not IFS is exported doesn't matter for this discussion.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
Ok os heres my situation. I have created a database style program that stores a persons info (name,address,phone number etc.) in a file ("database"). after i read in all the values above, i assign them to a line variable:
line="$name^$address^$phonenum" >> phonebuk
as you can see... (1 Reply)
Discussion started by: djt0506
1 Replies
2. UNIX for Dummies Questions & Answers
Hi!
I am working in korn shell. I want to reset the dimiliter for the set command to "|" but instead of a command prompt return I am getting something as below
After issuing the command I am getting this....as if the shell is expecting something else. Can anybody suggest what's the problem.
... (2 Replies)
Discussion started by: udiptya
2 Replies
3. Shell Programming and Scripting
hi i am a learner
can some explain "export IFS=$(echo "\n\t\a")"
i am not able to understand the functionality
please help
thanks
Satya (1 Reply)
Discussion started by: Satyak
1 Replies
4. Shell Programming and Scripting
im messing up somehwere...and can't seem to clean up the script...for it to work
objectives:
1. check for today's file, and sleep 30 secs between retries
2. only allow 5 tries before script should fail.
3. if today's file found, wait 30 seconds for it to process..
code:
count=0... (8 Replies)
Discussion started by: sigh2010
8 Replies
5. Shell Programming and Scripting
Hi,
This is out of curiosity:
I wanted to extract year, month and date from a variable, and thought that combining read and IFS would help, but this doesn't work:
echo "2010 10 12" | read y m d
I could extract the parts of the date when separated by a -, and setting IFS in a subshell:
... (3 Replies)
Discussion started by: raphinou
3 Replies
6. Shell Programming and Scripting
Given the scenario like this, if at all if have to use IFS on the below given example, how it should be used.
IFS=/
eg:
/xyz/123/348/file1
I want to use the last slash /file1 . So can anyone, suggest me how to pick the last "/" as a IFS. (4 Replies)
Discussion started by: raghunsi
4 Replies
7. Shell Programming and Scripting
Hi,
while ; do
echo "Please enter "
read enter
yyyy=${enter:0:4}
mm=${enter:5:2}
dd=${enter:8:2}
result=`validateDate $yyyy $mm $dd`
When does the loop keeping repeating till?? till 1 is equal to 1?
what does this mean "${enter:0:4}" .The 0 and 4 part??
... (3 Replies)
Discussion started by: sid22
3 Replies
8. Shell Programming and Scripting
hi I keep getting an error with this nested if statement and am getting the error unexpected end of file, can anyone help me as to why this wont execute?
#!/bin/bash
#script to check wether the -i -v statements run correctly
removeFile ()
{
mv $1 $HOME/deleted
}... (3 Replies)
Discussion started by: somersetdan
3 Replies
9. Shell Programming and Scripting
I am using bash and resetting IFS as below when reading the command line arguments. I do this so I can call my script as in Ex1.
Ex1: ./synt2d-ray3dmod.bash --xsrc=12/20/30
This allows me to split both sides so that when I do "shift"
I can get 12/20/30
What I do not understand is... (21 Replies)
Discussion started by: kristinu
21 Replies
10. Shell Programming and Scripting
Hello masters of scripting,
I've been working to develop some basic monitoring scripts. I have solved one problem, but want to know how to solve the other.
I have a script that runs locally to create an output file with the Linux system kernel paramters, preceeded by the system name:
... (2 Replies)
Discussion started by: LinuxRacr
2 Replies
LEARN ABOUT OSX
ssl_ctx_new
SSL_CTX_new(3) OpenSSL SSL_CTX_new(3)
NAME
SSL_CTX_new - create a new SSL_CTX object as framework for TLS/SSL enabled functions
SYNOPSIS
#include <openssl/ssl.h>
SSL_CTX *SSL_CTX_new(SSL_METHOD *method);
DESCRIPTION
SSL_CTX_new() creates a new SSL_CTX object as framework to establish TLS/SSL enabled connections.
NOTES
The SSL_CTX object uses method as connection method. The methods exist in a generic type (for client and server use), a server only type,
and a client only type. method can be of the following types:
SSLv2_method(void), SSLv2_server_method(void), SSLv2_client_method(void)
A TLS/SSL connection established with these methods will only understand the SSLv2 protocol. A client will send out SSLv2 client hello
messages and will also indicate that it only understand SSLv2. A server will only understand SSLv2 client hello messages.
SSLv3_method(void), SSLv3_server_method(void), SSLv3_client_method(void)
A TLS/SSL connection established with these methods will only understand the SSLv3 protocol. A client will send out SSLv3 client hello
messages and will indicate that it only understands SSLv3. A server will only understand SSLv3 client hello messages. This especially
means, that it will not understand SSLv2 client hello messages which are widely used for compatibility reasons, see SSLv23_*_method().
TLSv1_method(void), TLSv1_server_method(void), TLSv1_client_method(void)
A TLS/SSL connection established with these methods will only understand the TLSv1 protocol. A client will send out TLSv1 client hello
messages and will indicate that it only understands TLSv1. A server will only understand TLSv1 client hello messages. This especially
means, that it will not understand SSLv2 client hello messages which are widely used for compatibility reasons, see SSLv23_*_method().
It will also not understand SSLv3 client hello messages.
SSLv23_method(void), SSLv23_server_method(void), SSLv23_client_method(void)
A TLS/SSL connection established with these methods will understand the SSLv2, SSLv3, and TLSv1 protocol. A client will send out SSLv2
client hello messages and will indicate that it also understands SSLv3 and TLSv1. A server will understand SSLv2, SSLv3, and TLSv1
client hello messages. This is the best choice when compatibility is a concern.
The list of protocols available can later be limited using the SSL_OP_NO_SSLv2, SSL_OP_NO_SSLv3, SSL_OP_NO_TLSv1 options of the
SSL_CTX_set_options() or SSL_set_options() functions. Using these options it is possible to choose e.g. SSLv23_server_method() and be able
to negotiate with all possible clients, but to only allow newer protocols like SSLv3 or TLSv1.
SSL_CTX_new() initializes the list of ciphers, the session cache setting, the callbacks, the keys and certificates, and the options to its
default values.
RETURN VALUES
The following return values can occur:
NULL
The creation of a new SSL_CTX object failed. Check the error stack to find out the reason.
Pointer to an SSL_CTX object
The return value points to an allocated SSL_CTX object.
SEE ALSO
SSL_CTX_free(3), SSL_accept(3), ssl(3), SSL_set_connect_state(3)
50 2013-03-05 SSL_CTX_new(3)