Different epoch conversion result for bash and csh users
Hi there
I'm using this script to convert command line history with Epoch time stamp to human readable. While it works fine with users with /bin/csh shell, it fails to convert for users with /bin/bash shell. Why is this happening? I even changed and added * and [0-9] after the # but it still didnt work..any idea what I'm doing wrong?
This is how the original history log look like:
These are my failed attempts
Meanwhile for csh users, I am getting converted logs
Could it be because the csh users' history logs have a plus sign "+" but the bash users' dont have the "+" sign?
hello gurus,
i want a perl/shell script which once invoked should convert a set of EPOCH timestamps to local time ( IST..i want) .
how does it work ,i have an idea on that..but writing a perl/shell script for it is not possible for me...so i need help for the same.
my exact requirement is... (2 Replies)
Having been a long-time csh person I now need to convert a lot of stuff to run under ksh. Can anyone tell me how to do a ksh equivalent of the csh history substitution !* that can be used in an alias, ie how would I do:
alias cd "cd \!*; pwd"
alias find "find . -name... (2 Replies)
Hi,
1st post...
Done a quick search for this so apologies if I've missed it.
Basically I want to output and and append several values generated by a csh script direct to an xls openoffice file, rather than send to txt file and then physically copy and paste to xls file.
Already I send... (4 Replies)
Hello all. I'm a long time browser, first time poster...Be gentle :-)
I don't use csh much, but have been asked to make a small script for our HP-UX systems to search for a report file(s) or summary file and display the result (I was using vuepad, but this probably is just
complicating... (4 Replies)
Can someone tell me why I'm getting error when I try to run this?
#!/bin/csh -f
source ~/.cshrc
#
set SQLPLUS = ${ORACLE_HOME}/bin/sqlplus
#
set count=`$SQLPLUS -s ${DB_LOGIN} << END
select count(1) from put_groups where group_name='PC' and description='EOD_EVENT' and serial_number=1;... (7 Replies)
I need to convert an epoch time from a file into a standard UTC time and output it in the same format but I'm not sure what's the best approach
here's the input file and the bold part is what I need to convert.
1,1,"sys1",60,300000
2,"E:",286511144960
3,1251194521,"E:",0,0... (2 Replies)
I am trying get time difference of two dates in secs. Initially I want to convert a standard date format to epoch for two dates and then subtract the two epoch dates.
Example :
date -d "2007-09-01 17:30:40" '+%s'
But this gives me below error
date: illegal option -- d
Usage: date
OS: AIX... (6 Replies)
Hi All,
Please read the below data carefully.
I need an unix command for converting unix timestamp to Epoch timestamp.
I need to daily convert this today's unix(UTC) time to epoch time, so i am thinking to make a shellscript for this.
Please help me for this by providing... (3 Replies)
Hi there
I came across this script online to convert Epoch time to proper date format, but I am receiving the following error
Also, I have HISTTIMEFORMAT set in user's .profile so that their history output shows time stamps. Additionally I have changed their .history location to a dedicated... (9 Replies)
Hi. I have timestamps that I am trying to convert to epoch time. An example:
I am trying to convert this to an epoch timestamp but have one little glitch. I have this:
import time
date_time = ''
pattern = ''
epoch = int(time.mktime(time.strptime(date_time, pattern)))
print epoch... (1 Reply)
Discussion started by: treesloth
1 Replies
LEARN ABOUT DEBIAN
colorgccrc
COLORGCCRC(5) File Formats Manual COLORGCCRC(5)NAME
colorgccrc - configuration file for colorgcc
DESCRIPTION
A colorgccrc configuration file is used to configure the highlighting of the compiler output from colorgcc.
SYNTAX
Each line consists of a keyword designating a configuration variable. The keyword is followed by `:' and then one or several values
(depending on the keyword). Lines beginning with a hash mark `#' are comments.
CONFIGURATION VARIABLES
g++ | gcc | c++ | cc | g77 | gcj | gnat | gpc
Specifies the paths to the compilers. Takes one value; a path to the compiler.
nocolor
Specifies what terminal types colorization should be disabled on. Takes one or several values, separated by whitespace.
srcColor
Specifies the highlighting attributes source-code should be given. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
introColor
Specifies the highlighting attributes for normal compiler output. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
warningFileNameColor | errorFileNameColor
Specifies the highlighting attributes for the filename in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningNumberColor | errorNumberColor
Specifies the highlighting attributes for the line-number in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningMessageColor | errorMessageColor
Specifies the highlighting attributes for the message-text in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
COLOR ATTRIBUTES
The following attributes are valid for highlighting.
clear, reset
bold, underline, underscore, blink, reverse, concealed
black, red, green, yellow, blue, magenta, cyan, white
on_black, on_red, on_green, on_yellow, on_blue, on_magenta, on_cyan, on_white
SEE ALSO gcc(1), colorgcc(1)HISTORY
Jan 15 2003: Initial version of this manual-page.
REPORTING BUGS
Report bugs to <jmoyers@geeks.com>
AUTHORS
Jamie Moyers <jmoyers@geeks.com> is the author of colorgcc.
This manual page was written by Joe Wreschnig <piman@sacredchao.net>, and modified by David Weinehall <tao@debian.org>, for the Debian
GNU/Linux system (but may be used by others).
COPYRIGHT
Copyright (C) 2003 Jamie Moyers
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Jan 15, 2003 COLORGCCRC(5)