Hi Alexandar:
On Thu, Nov 7, 2013 at 7:27 PM, Aleksandar Kuktin wrote:
> I can [replicate the "Oops" after all].
>
Guess the clock change was on 2013-10-27th where I am.
>
> That's one of the problems I have with Dan's suggestion (_instinctively_.
As I said,
I haven't give it any thought at al
>On Thu, 7 Nov 2013 16:02:43 -0500
>alex lupu wrote:
>
> [snip]
>
> []% date
> Thu Nov 7 13:05:10 EST 2013
> []% hrs2date 2013-11-07
> toDATEhrs = 13
> []% hrs2date 2013-11-06
> toDATEhrs = 37
> []% hrs2date 2013-11-05
> toDATEhrs = 61
> []% hrs2date 2013-11-04
> toDATEhrs = 85
> []% hrs2date 2
>On Thu, 7 Nov 2013 16:02:43 -0500
>alex lupu wrote:
> [snip]
> #!/bin/bash
> # hrs2date
> if [ "$1" == "" ]; then
> # for people who didn't read my post
> echo "Enter a date (-mm-dd)" ; exit 2
> fi
>
> DATE=$1
>
> NOWsecs=`date +%s` # This moment (in sec. since
> Jan
Hi Dan:
On Thu, Nov 7, 2013 at 4:37 PM, Dan McGhee wrote:
> When I got to the end of your post and you wondered about a "simple"
> command, my mind went right back to these two statements. This is also
> just a "gut reaction" to your post and not thought out. (I'm taking a
> break from trying
On 11/07/2013 03:02 PM, alex lupu wrote:
A sample output:
[]% date
Thu Nov 7 13:05:10 EST 2013
Note: the time change (DST to EST) was effected at 2AM, Nov. 3 here,
whereby everybody had to move their clocks one hour back - like to 1AM.
When I got to the end of your post and you wondered ab
Hi everybody:
WARNING - this is a lengthy post. Can be safely skipped.
In my previous posts, I expressed my puzzlement/sadness about a construct
like
# Gimme the files modified in the range between n and m minutes ago
find -mmin -n -mmin +m
not working for me.
As always, Bruce showed me that
>
> Richard Melville wrote:
> > Looking through the *setting up a network firewall* page I wondered what
> > the thinking was behind switching the kernel parameters via an
> rc.iptables
> > file rather than the perhaps more conventional sysctl.conf file.
>
> It's more straight forward and it stands
