Hi Maykel,
> > This will remove the carriage returns at the end of lines once
> > script has finished.
>
> This not working. Not quit the end file log character "^M"
>
> > script -f -c '/usr/local/bin/cccam -d' mylogfile.log
> > sed -i 's/\r$//' mylogfile.log
It works here.
$ script
El sáb., 2 mar. 2019 a las 10:23, Ralph Corderoy
() escribió:
>
> Hi Maykel,
>
> > Now only remove ^M character from log files in buffer time but this
> > not working:
> >
> > script -f -c '/usr/local/bin/cccam -d' mylogfile.log | sed 's/^M//g'
>
> script(1) writes to mylogfile.log, sed sees no inp
Hi Maykel,
> Now only remove ^M character from log files in buffer time but this
> not working:
>
> script -f -c '/usr/local/bin/cccam -d' mylogfile.log | sed 's/^M//g'
script(1) writes to mylogfile.log, sed sees no input.
This will remove the carriage returns at the end of lines once script
has
Hi Maykel,
> > > > Otherwise, `LC_ALL=C strace -ff -o st /usr/local/bin/CCcam -d'
> > > > will capture the write(2)s or similar and you can see what file
> > > > descriptors its writing to and work backwards to see how that
> > > > was obtained, e.g. by opening /dev/tty.
> > >
> > > Nothing happen
El vie., 1 mar. 2019 a las 21:49, Chris Billington
() escribió:
>
> The output of the script command can contain all sorts of control characters
> and ANSI escape sequences since it is exactly what is being written to the
> terminal.
>
> Incidentally, I have written a Python function for cleaning
The output of the script command can contain all sorts of control
characters and ANSI escape sequences since it is exactly what is being
written to the terminal.
Incidentally, I have written a Python function for cleaning up such output
(solely used to document my Arch linux installation):
https:
El vie., 1 mar. 2019 a las 21:32, Chris Billington
() escribió:
>
> The 'flush' option could help with that:
> [bilbo:~]$ script -h | grep flush
> -f, --flush run flush after each write
>
> So, something like
>
> script -f -c '/usr/local/bin/cccam -d' mylogfile.log
>
> I would wa
The 'flush' option could help with that:
[bilbo:~]$ script -h | grep flush
-f, --flush run flush after each write
So, something like
script -f -c '/usr/local/bin/cccam -d' mylogfile.log
I would want to get to the bottom of why this binary does not play well
with normal tools,
El vie., 1 mar. 2019 a las 20:08, Chris Billington
() escribió:
>
> This is pretty strange.
>
> As for the script command, it can be passed the command to run, but I am
> guessing it will have the same symptoms as with 'unbuffer':
>
> [bilbo:~]$ script -c 'echo hello' mylogfile.log
> Script starte
This is pretty strange.
As for the script command, it can be passed the command to run, but I am
guessing it will have the same symptoms as with 'unbuffer':
[bilbo:~]$ script -c 'echo hello' mylogfile.log
Script started, file is mylogfile.log
hello
Script done, file is mylogfile.log
[bilbo:~]$ ca
El vie., 1 mar. 2019 a las 19:30, Ralph Corderoy
() escribió:
>
> Hi Maykel,
>
> > > command &> out
> >
> > Not works... I probe all combinations:
> >
> > > file redirects stdout to file
> > 1> file redirects stdout to file
> > 2> file redirects stderr to file
> > &> file redirects stdout and stder
Hi Maykel,
> > command &> out
>
> Not works... I probe all combinations:
>
> > file redirects stdout to file
> 1> file redirects stdout to file
> 2> file redirects stderr to file
> &> file redirects stdout and stderr to file
Can you show us one complete command with `&>' in case there's something
El vie., 1 mar. 2019 a las 19:15, Chris Billington
() escribió:
>
> Perplexing! How about the 'script' command?
>
> On Fri., 1 Mar. 2019, 13:13 Maykel Franco, wrote:
>>
>> El vie., 1 mar. 2019 a las 19:09, Chris Billington
>> () escribió:
>> >
>> > The program could also explicitly be modifying it
Perplexing! How about the 'script' command?
On Fri., 1 Mar. 2019, 13:13 Maykel Franco, wrote:
> El vie., 1 mar. 2019 a las 19:09, Chris Billington
> () escribió:
> >
> > The program could also explicitly be modifying its behaviour based on
> whether stdout is a tty or not. You can trick it into
El vie., 1 mar. 2019 a las 19:09, Chris Billington
() escribió:
>
> The program could also explicitly be modifying its behaviour based on whether
> stdout is a tty or not. You can trick it into thinking its stdout is a tty
> with the program 'unbuffer'. For example:
>
> [bilbo:~]$ python -c 'impo
The program could also explicitly be modifying its behaviour based on
whether stdout is a tty or not. You can trick it into thinking its stdout
is a tty with the program 'unbuffer'. For example:
[bilbo:~]$ python -c 'import sys; print(sys.stdout.isatty())' | cat
False
[bilbo:~]$ unbuffer python -c
El vie., 1 mar. 2019 a las 19:01, Chris Billington
() escribió:
>
> Perhaps the program writes its log to stderr, and not to stdout?
>
> If so, you can redirect both stdout and stderr to file with:
>
> command &> out
>
>
>
> On Fri, Mar 1, 2019 at 12:47 PM Maykel Franco via arch-general
> wrote:
Hi Maykel,
> I playing with cccam for a proyect with decoder and I like stdout
> console log to specific log but not work...
>
> I try all:
>
> >> /var/log/test.log
Have you seen
https://wiki.archlinux.org/index.php/Command-line_shell#Input_and_output
and the links it provides?
--
Cheers, R
Perhaps the program writes its log to stderr, and not to stdout?
If so, you can redirect both stdout and stderr to file with:
command &> out
On Fri, Mar 1, 2019 at 12:47 PM Maykel Franco via arch-general <
arch-general@archlinux.org> wrote:
> HI, I playing with cccam for a proyect with decode
HI, I playing with cccam for a proyect with decoder and I like stdout
console log to specific log but not work...
I try all:
>> /var/log/test.log
tee -a /var/log/test.log
strace -p pid
The command is:
/usr/local/bin/CCcam -d
18:43:15.717 CCcam:
20 matches
Mail list logo
