On Dec 4, 9:28 am, pjodrr pjo...@gmail.com wrote:
Hello,
how can I prefix every line of output of some command with a
timestamp? I thought like this:
$ exec 3 (while read line; do echo $(date): $line; done)
$ seq 4 3
Friday, December 4, 2009 4:20:29 PM MET: 1
$ Friday, December 4,
pjodrr wrote:
Hello,
how can I prefix every line of output of some command with a
timestamp? I thought like this:
$ exec 3 (while read line; do echo $(date): $line; done)
$ seq 4 3
Friday, December 4, 2009 4:20:29 PM MET: 1
$ Friday, December 4, 2009 4:20:29 PM MET: 2
Friday,
On Dec 4, 12:58 pm, pk p...@pk.invalid wrote:
pjodrr wrote:
Hello,
how can I prefix every line of output of some command with a
timestamp? I thought like this:
$ exec 3 (while read line; do echo $(date): $line; done)
$ seq 4 3
Friday, December 4, 2009 4:20:29 PM MET: 1
$
Hi, bash folks,
for a larger shell-based project I wanted to have definit answers to questions
like
- are all redirections to log handle 3 done when the log handle is actually
open?
- are all calls to grep handled properly (either return value or output
ignored)?
- are all calls to exit
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale'
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale'
Hello,
how can I prefix every line of output of some command with a
timestamp? I thought like this:
$ exec 3 (while read line; do echo $(date): $line; done)
$ seq 4 3
Friday, December 4, 2009 4:20:29 PM MET: 1
$ Friday, December 4, 2009 4:20:29 PM MET: 2
Friday, December 4, 2009 4:20:29
Michael O'Donnell wrote:
A bash function with a dot in its name can be created and used with no
problems but cannot be removed - the unset command chokes on the name.
Repeat-By:
This sequence yields the expected results:
function f() { echo $FUNCNAME ; }
f
unset f
I'd like to dispatch commands from one light-weight bash process to a
longer running bash process which takes longer to initialize [ I have
a _big_ library of bash functions ].
On Linux or any reasonable OS, I could do this remote dispatch easily
with named pipes, but these don't exist on
On Dec 4, 9:25 am, Michael O'Donnell mod.bash...@b0rken.com wrote:
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jon Seymour on 12/4/2009 4:00 PM:
On Linux or any reasonable OS, I could do this remote dispatch easily
with named pipes, but these don't exist on cygwin.
That's where you're wrong. Named pipes DO exist on cygwin, although there
are
Oh, cool. Thanks for correcting me!
jon.
On Sat, Dec 5, 2009 at 11:54 AM, Eric Blake e...@byu.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jon Seymour on 12/4/2009 4:00 PM:
On Linux or any reasonable OS, I could do this remote dispatch easily
with named pipes, but
Michael O'Donnell wrote:
Bash Version: 4.0
Patch Level: 28
Release Status: release
Description:
A bash function with a dot in its name can be created and used with no
problems but cannot be removed - the unset command chokes on the name.
It's true -- the shell allows you to define a
13 matches
Mail list logo
