The problem I have is trying to match multiple lines using sed or egrep, so I did not quickly find a way to filter out the Explanation text. The rest was easy (plus I removed the stray number and the "New questions" phrase):
Leaving an incomplete solution because of the requirement for a multiline regex match:
In practice, I would do this in PERL or PHP because of the required multiline matches; but I'm sure someone else can do a much better command line than me.
I am about 2 months new to Linux, and have only limited experience with PCLinuxOS, (kde) and Redhat.
I am installing the latest version of PClinuxOS on my wife's PC right now but running into a problem I dont understand. I have never seen it before so i thought i'd ask how I can get around it.... (1 Reply)
hi all
plese clarify me in the following area.
1. What is the default NFS version in solaris 5.10. If it is 3, then why it asks me to specify "-o vers=3" keyword while i am mounting a share from a RHEL 5.1 Server?
2. Can someone give the link to download packages for accessing "ntfs"... (4 Replies)
Hello,
I am new to this forum and I am preparing for interview .Kindly can anybody send me Solaris 10 OS administration interview questions and answers (2 Replies)
Hey you guys,
There's a couple questions I cannot find the answers to anywhere in this book for my Operating Systems class, hopefully you guys could help. I believe we are in the Bourne shell.
1. Match each description to the appropriate type of variable
Used in shell programs
... (7 Replies)
Discussion started by: KyleBucket
7 Replies
6. Post Here to Contact Site Administrators and Moderators
I hope this is ok so I will ask if I may use this thread to ask questions about
programming.
May I use this thread to ask questions and answer questions?
If the answer is yes, this is a thread made for minimizing the amount of threads I post to
ask questions about programming. Please feel... (3 Replies)
Hi all,
I have a fat file which contains something like this:
************************************************
blahblahblah
blahblahblah
Myobject1 HOME (
homecontents01 (
some junk;
)
home contents02(
some junk;
)
... (7 Replies)
Hi Unix geniuses,
I need your help for the answers of few objective Q&A.
i dont know if my answers are correct or not.
So i really need your help to provide the answers which will help me in unix programming. (1 Reply)
Here are some answers to some of the recent questions I have received about UNIX.COM. So, I thought I would take time to answer them here in this post:
Is it expected that the original poster "thank" everyone who responds to his / her discussion thread?
It is always a good practice in all... (7 Replies)
Discussion started by: Neo
7 Replies
LEARN ABOUT HPUX
gss_inquire_context
gss_inquire_context(3) Library Functions Manual gss_inquire_context(3)NAME
gss_inquire_context() - obtain information about a security context
SYNOPSIS DESCRIPTION
The routine provides information about the security context to the calling application. The calling application must first have called the
routine for a handle for the credential.
Input Parameters
context_handle A handle that refers to the security context.
Output Parameters
src_name The name of the context initiator. If the context was established using anonymous authentication, and if the appli-
cation invoking is the context acceptor, an anonymous name will be returned. Specify NULL if not required.
context_handle The name of the context acceptor. If the context acceptor did not authenticate itself, and if the initiator did not
specify a target name in its call to the value will be returned. Specify NULL if not required.
lifetime_rec Returns the number of seconds for which the credential will remain valid. If the credential expired, the parameter
returns a 0 (zero). If there is no credential expiration, the parameter returns the value If an expiration time is
not required, specify NULL.
targ_name The name of the context acceptor. Storage associated with this name must be freed by the application after use with
a call to
mech_type The security mechanism providing the context. Specify NULL if not required
ctx_flags Specifies independent flags, each of which requests that the context support a service option. The following sym-
bolic names are provided to correspond to each flag. The symbolic names should be logically ORed to form a bit-mask
value.
The True/False values are:
True Credentials were delegated to the context acceptor.
False No credentials were delegated.
The True/False values are:
True The context acceptor has been asked to authenticate itself.
False The context initiator has not been asked to authenticates itself.
The True/False values are:
True Replayed signed or sealed messages will be detected.
False Replayed messages will not be detected.
The True/False values are:
True Out-of-sequence signed or sealed messages will be detected.
False Out-of-sequence signed or sealed messages will not be detected.
The True/False values are:
True Request that confidentiality service be made available
False No per-message confidentiality service is required.
The True/False values are:
True Request that integrity service be be made available
False No per-message integrity service is required.
The True/False values are:
True Do not reveal the initiator's identity to the acceptor.
False Authenticate normally.
cred_usage Returns one of the following values describing how the application can use the credential:
If no usage information is required, specify NULL.
mechs returns a set of security mechanisms supported by the credential. Specify NULL if not required.
minor_status Returns a status code from the security mechanism.
STATUS CODES
The following status codes can be returned:
The routine was completed successfully.
The referenced context could not be accessed.
The credentials were invalid.
The routine failed. Check the
minor_status parameter for details.
The routine could not access the credentials.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO gss_acquire_cred(3).
The manpages for DCE-GSSAPI are included with the DCE-CoreTools product. To see those manpages add to
gss_inquire_context(3)