Sponsored Content
Full Discussion: Timestamp in AIX Prompt
Operating Systems AIX Timestamp in AIX Prompt Post 302441010 by royalibrahim on Thursday 29th of July 2010 06:19:48 AM
Old 07-29-2010
Code:
export PS1="[`date +%T`] "

But, I am not sure how to refresh the time.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX/awk date to unix timestamp

Hello, I am inside a awk script on AIX, I am feeding to awk ls -luNR i need to convert ls -u time format "month day h:m/yr" to Unix epoch time, POSIX time, or aka unix timestamp I do not have strftime funk in my awk, and i have to do this fast meaning that I cannot do a system call in the... (1 Reply)
Discussion started by: nullwhat
1 Replies

2. Shell Programming and Scripting

Command to get File Timestamp including seconds [Aix 5.3]

Is there a command (like ls -l) to get the file time stamp including seconds? The ls -l gives only the HH:MM, No SS I don't have a C compiler to call stat() I don't a command like stat too. Please help. (8 Replies)
Discussion started by: firdousamir
8 Replies

3. AIX

Custom AIX Prompt

In my .profile, my prompt is set like this: set -o vi PS1=`logname`@`hostname -s`:'$PWD>' Is there a way to show what the history number would be of the command I'm typing in the prompt? For example, I frequently run commands then run 'history' to pull up the history number of a command... (2 Replies)
Discussion started by: ptrotter
2 Replies

4. Shell Programming and Scripting

How to get a Prompt (PS1) Timestamp under /sbin/sh?

Hi, I'm trying to find out if there is a way to get a timestamp on my Solaris root shell prompt using /sbin/sh? I'm trying to archive something in line with the following: 12:34:26 root@server # 12:34:28 root@server # 12:34:28 root@server # ls ... 12:34:30 root@server # I know there... (1 Reply)
Discussion started by: Solarius
1 Replies

5. UNIX for Dummies Questions & Answers

scp not working because of prompt (AIX, tcsh)

Hello, I have this problem: I have a server to which I ssh, and it has a special prompt request. The prompt is done by a ?prompt command. It is fine with SSH, since the prompt I guess gets some input, but when I use SCP, the copy always fails. So, I was wondering if there is maybe a... (1 Reply)
Discussion started by: lastZenMaster
1 Replies

6. AIX

ssh keys - no password prompt from AIX to RPA

hello, i am running an AIX 5.3 machine and i want to connect via ssh to the RPA Management site without prompting for password. i already had a public key of this server as i use the same thing for ssh connection with other AIX machines. i connected to the RPA Management Site and i run the... (9 Replies)
Discussion started by: omonoiatis9
9 Replies

7. AIX

how many su - users I ejecute in prompt AIX 5.3

Hi Colleagues, My English is pretty bad, the help I need is this: entered into a machine with OS AIX 5.3 and i execute su - user1 and then i execute su - user2 and then i execute su - user3 and finally its su - user4. there is some command that tells me the its that i have made? Thank you... (2 Replies)
Discussion started by: systemoper
2 Replies

8. Shell Programming and Scripting

To check timestamp in logfile and display lines upto 3 hours before current timestamp

Hi Friends, I have the following logfile. Currently time in india is 07/31/2014 12:33:34 and i have the following content in logfile. I want to display only those entries which contain string 'Exception' within last 3 hours. In this case, it would be the last line only I can get the... (12 Replies)
Discussion started by: srkmish
12 Replies

9. Shell Programming and Scripting

AIX : Need to convert UNIX Timestamp to normal timestamp

Hello , I am working on AIX. I have to convert Unix timestamp to normal timestamp. Below is the file. The Unix timestamp will always be preceded by EFFECTIVE_TIME as first field as shown and there could be multiple EFFECTIVE_TIME in the file : 3.txt Contents of... (6 Replies)
Discussion started by: rahul2662
6 Replies

10. Emergency UNIX and Linux Support

AIX prompt delayed when users increase

I am facing a situation where when there are lesser users, i am able to login to the AIX server. If the number of users increase - the login prompt is getting delayed. Sometimes even timeout occurs. This is after the upgrade to AIX 7.1 TL 4. Can someone suggest a way to overcome this situation? (6 Replies)
Discussion started by: ggayathri
6 Replies
Env::PS1(3pm)						User Contributed Perl Documentation					     Env::PS1(3pm)

NAME
Env::PS1 - prompt string formatter SYNOPSIS
# use the import function use Env::PS1 qw/$PS1/; $ENV{PS1} = 'u@h $ '; print $PS1; $readline = <STDIN>; # or tie it yourself tie $prompt, 'Env::PS1', 'PS1'; # you can also tie a scalar ref $format = 'u@h$ '; tie $prompt, 'Env::PS1', $format; DESCRIPTION
This package supplies variables that are "tied" to environment variables like 'PS1' and 'PS2', if read it takes the contents of the variable as a format string like the ones bash(1) uses to format the prompt. It is intended to be used in combination with the various ReadLine packages. EXPORT
You can request for arbitrary variables to be exported, they will be tied to the environment variables of the same name. TIE
When you "tie" a variable you can supply one argument which can either be the name of an environement variable or a SCALAR reference. This argument defaults to 'PS1'. METHODS
"sprintf($format)" Returns the formatted string. Using this method all the time is a lot less efficient then using the tied variable, because the tied variable caches parts of the format that remain the same anyway. FORMAT
The format is copied mostly from bash(1) because that's what it is supposed to be compatible with. We made some private extensions which obviously are not portable. Note that this is not the prompt format as specified by the posix specification, that would only know "!" for the history number and "!!" for a literal "!". Apart from the escape sequences you can also use environment variables in the format string; use $VAR or "${VAR}". The following escape sequences are recognized: a The bell character, identical to "07" d The date in "Weekday Month Date" format D{format} The date in strftime(3) format, uses POSIX e The escape character, identical to "33" Newline Carriage return s The basename of $0 The current time in 24-hour format, identical to "D{%H:%M:%S}" T The current time in 12-hour format, identical to "D{%I:%M:%S}" @ The current time in 12-hour am/pm format, identical to "D{%I:%M %p}" A The current time in short 24-hour format, identical to "D{%H:%M}" u The username of the current user w The current working directory W The basename of the current working directory $ "#" for effective uid is 0 (root), else "$" dd The character corresponding to the octal number 0dd \ Literal backslash H Hostname, uses Sys::Hostname h First part of the hostname l The basename of the (output) terminal device name, uses POSIX, but won't be really portable. [ ] These are used to encapsulate a sequence of non-printing chars. Since we don't need that, they are removed. Extensions The following escapes are extensions not supported by bash, and are not portable: L The (output) terminal device name, uses POSIX, but won't be really portable. C{colour} Insert the ANSI sequence for named colour. Known colours are: black, red, green, yellow, blue, magenta, cyan and white; background colours prefixed with "on_". Also known are reset, bold, dark, underline, blink and reverse, although the effect depends on the terminla you use. Unless you want the whole commandline coloured you should end your prompt with "C{reset}". Of course you can still use the "raw" ansi escape codes for these colours. Note that "bold" is sometimes also known as "bright", so "C{bold,black}" will on some terminals render dark grey. If the environment variable "CLICOLOR" is defined but false colours are switched off automaticly. P{format} Proc information. All of these are unix specific %a Acpi AC status '+' or '-' for connected or not, linux specific %b Acpi battery status in mWh, linux specific %L Load average %l First number of the load average %t Acpi temperature, linux specific %u Uptime %w Number of users logged in Not implemented escapes The following escapes are not implemented, because they are application specific. j The number of jobs currently managed by the application. v The version of the application. V The release number of the application, version + patchelvel ! The history number of the next command. This escape gets replaced by literal '!' while a literal '!' gets replaces by '!!'; this makes the string a posix compatible prompt, thus it will work if your readline module expects a posix prompt. # The command number of the next command (like history number, but minus the lines read from the history file). Customizing If you want to overload escapes or want to supply values for the application specific escapes you can put them in %Env::PS1::map, the key is the escape letter, the value either a string or a CODE ref. If you map a CODE ref it normally is called every time the prompt string is read. When the escape is followed by an argument in the format string (like "D{argument}") the CODE ref is called only once when the string is cached, but in that case it may in turn return a CODE ref. BUGS
Please mail the author if you encounter any bugs. AUTHOR
Jaap Karssenberg || Pardus [Larus] <pardus@cpan.org> This module is currently maintained by Ryan Niebur <rsn@cpan.org> Copyright (c) 2004 Jaap G Karssenberg. All rights reserved. Copyright (c) 2009 Ryan Niebur. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Env, Term::ReadLine::Zoid perl v5.10.0 2009-06-25 Env::PS1(3pm)
All times are GMT -4. The time now is 08:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy