9 More Discussions You Might Find Interesting
1. Red Hat
Hi,
I tried to execute a command to check if
Kerberos server is enabled
Printer Daemon is enabled
GUI Login is enabled,
do advise how I check from the logs below on how to check whether the commands are valid or not?
ls -all /etc/rc2.d/
total 8
drwxr-xr-x. 2 root root... (2 Replies)
Discussion started by: alvinoo
2 Replies
2. Solaris
Hi, was wondering if its possible to change the default warning message text that notifies users that their kerberos ticket is due to expire in xx minutes. I am using Kerberos 5 on Sol 10.
Can't find anything in man pages, so hoping its maybe an undocumented feature. I'd like to make the... (1 Reply)
Discussion started by: melias
1 Replies
3. Shell Programming and Scripting
How to check log size every 10min. by script (can use crontab)
if log size not change with alert "Log not update"
Base run on SunOS 5.8 Generic_Virtual sun4u sparc SUNW,SPARC-Enterprise
logFiles="log1.log log2.log"
logLocation="/usr/home/test/log/"
Out put.
Tue Jan 31... (3 Replies)
Discussion started by: ooilinlove
3 Replies
4. Linux
This is more of an annoyance than an actual production issue. I've set it up so that each user's home directory is mounted to an immediate subdirectory of $HOME when they login, (and umounts when they log out to keep /proc/mounts a manageable size).
My issue comes in when my login scripts... (0 Replies)
Discussion started by: thmnetwork
0 Replies
5. HP-UX
AM in need of some plugin/script that can monitor HP-UX file "/var/opt/resmon/log/event.log" .
Have written a scrip in sh shell that is working fine for syslog.log and mail.log as having standard format, have interrogated that to Nagios and is working as I required .
But same script failed to... (3 Replies)
Discussion started by: Shirishlnx
3 Replies
6. Shell Programming and Scripting
I've been finding myself using a log file colorizer written in perl to reformat and colorize the output from many different programs. Mainly, however, I use it to make the output from "tail -f" commands more readable.
The base perl script I use is based on "colorlogs.pl" available from the... (1 Reply)
Discussion started by: rcsteiner
1 Replies
7. Shell Programming and Scripting
Hi
I have a requirement to write a script to capture all errors in a Logfile and send the file in email.
If there is any error occurred the subject of email will be ERROR , If there are no error occurred the subject of email will be SUCCESS.
So I created a Log file and put the Appropriate... (2 Replies)
Discussion started by: dgmm
2 Replies
8. Shell Programming and Scripting
If a log file is in the following format
28-Jul-10 ::: Log message
28-Jul-10 ::: Log message
29-Jul-10 ::: Log message
30-Jul-10 ::: Log message
31-Jul-10 ::: Log message
31-Jul-10 ::: Log message
1-Aug-10 ::: Log message
1-Aug-10 ::: Log message
2-Aug-10 ::: Log message
2-Aug-10 :::... (3 Replies)
Discussion started by: vikram3.r
3 Replies
9. Shell Programming and Scripting
OK, so I've got some time on my hands due to a workplace injury, but due to a couple of broken bones and the good drugs, actually implementing something useful is proving challenging :(
I am playing with generating large numbers of Pick 6 lottery ticket combos. These are stored in tab-delimited... (1 Reply)
Discussion started by: mabman
1 Replies
KINIT(1) General Commands Manual KINIT(1)
NAME
kinit - obtain and cache Kerberos ticket-granting ticket
SYNOPSIS
kinit [-5] [-4] [-V] [-l lifetime] [-s start_time] [-r renewable_life] [-p | -P] [-f | -F] [-A] [-v] [-R] [-k [-t keytab_file]] [-c
cache_name] [-S service_name] [principal]
DESCRIPTION
kinit obtains and caches an initial ticket-granting ticket for principal.Thetypicaldefaultbehavioristoacquireonly Kerberos 5 tickets. How-
ever, if kinit was built with both Kerberos 4 support and with the default behavior of acquiring both types of tickets, it will try to
acquire both Kerberos 5 and Kerberos 4 by default. Any documentation particular to Kerberos 4 does not apply if Kerberos 4 support was not
built into kinit.
OPTIONS
-5 get Kerberos 5 tickets. This overrides whatever the default built-in behavior may be. This option may be used with -4
-4 get Kerberos 4 tickets. This overrides whatever the default built-in behavior may be. This option is only available if kinit was
built with Kerberos 4 compatibility. This option may be used with -5
-V display verbose output.
-l lifetime
requests a ticket with the lifetime lifetime. The value for lifetime must be followed immediately by one of the following delim-
iters:
s seconds
m minutes
h hours
d days
as in "kinit -l 90m". You cannot mix units; a value of `3h30m' will result in an error.
If the -l option is not specified, the default ticket lifetime (configured by each site) is used. Specifying a ticket lifetime
longer than the maximum ticket lifetime (configured by each site) results in a ticket with the maximum lifetime.
-s start_time
requests a postdated ticket, valid starting at start_time. Postdated tickets are issued with the invalid flag set, and need to be
fed back to the kdc before use. (Not applicable to Kerberos 4.)
-r renewable_life
requests renewable tickets, with a total lifetime of renewable_life. The duration is in the same format as the -l option, with the
same delimiters. (Not applicable to Kerberos 4.)
-f request forwardable tickets. (Not applicable to Kerberos 4.)
-F do not request forwardable tickets. (Not applicable to Kerberos 4.)
-p request proxiable tickets. (Not applicable to Kerberos 4.)
-P do not request proxiable tickets. (Not applicable to Kerberos 4.)
-A request address-less tickets. (Not applicable to Kerberos 4.)
-v requests that the ticket granting ticket in the cache (with the invalid flag set) be passed to the kdc for validation. If the
ticket is within its requested time range, the cache is replaced with the validated ticket. (Not applicable to Kerberos 4.)
-R requests renewal of the ticket-granting ticket. Note that an expired ticket cannot be renewed, even if the ticket is still within
its renewable life. When using this option with Kerberos 4, the kdc must support Kerberos 5 to Kerberos 4 ticket conversion.
-k [-t keytab_file]
requests a host ticket, obtained from a key in the local host's keytab file. The name and location of the keytab file may be speci-
fied with the -t keytab_file option; otherwise the default name and location will be used. When using this option with Kerberos 4,
the kdc must support Kerberos 5 to Kerberos 4 ticket conversion.
-c cache_name
use cache_name as the Kerberos 5 credentials (ticket) cache name and location; if this option is not used, the default cache name
and location are used.
The default credentials cache may vary between systems. If the KRB5CCNAME environment variable is set, its value is used to name
the default ticket cache. Any existing contents of the cache are destroyed by kinit. (Note: The default name for Kerberos 4 comes
from the KRBTKFILE environment variable. This option does not apply to Kerberos 4.)
-S service_name
specify an alternate service name to use when getting initial tickets. (Applicable to Kerberos 5 or if using both Kerberos 5 and
Kerberos 4 with a kdc that supports Kerberos 5 to Kerberos 4 ticket conversion.)
ENVIRONMENT
Kinit uses the following environment variables:
KRB5CCNAME Location of the Kerberos 5 credentials (ticket) cache.
KRBTKFILE Filename of the Kerberos 4 credentials (ticket) cache.
FILES
/tmp/krb5cc_[uid] default location of Kerberos 5 credentials cache ([uid] is the decimal UID of the user).
/tmp/tkt[uid] default location of Kerberos 4 credentials cache ([uid] is the decimal UID of the user).
/etc/krb5.keytab
default location for the local host's keytab file.
SEE ALSO
klist(1), kdestroy(1), krb5(3)
KINIT(1)