Re: How to know % of read file in cat?

> I use cat to read a file and pass it to another app, the command is this: > > camibar% cat file.git | fossil import --git file.fossil > > It takes a lot of time, file.git is 12GB, and i want to know if > there's some 'magic' trick can I use to show me how many

Re: How to know % of read file in cat?

You might want to try the sysutils/pv port, which is a small program that works like cat, but provides a progress bar. On Sat, Mar 09, 2013 at 10:54:00AM +0100, Eduardo Morras wrote: > > Hello, > > I use cat to read a file and pass it to another app, the command is this: >

Re: How to know % of read file in cat?

On Sat, 9 Mar 2013 11:11:26 +0100 Matthias Apitz wrote: > Yes, in your case cat(1) is superflues (see also the Useless Use of Cat > Award) because the correct way would be: > > camibar% fossil import --git file.fossil < file.git > > It depends of the tool 'fossil'

Re: How to know % of read file in cat?

On Sat, 9 Mar 2013 10:54:00 +0100, Eduardo Morras wrote: > > Hello, > > I use cat to read a file and pass it to another app, the command is this: > > camibar% cat file.git | fossil import --git file.fossil > > It takes a lot of time, file.git is 12GB, and i want t

Re: How to know % of read file in cat?

On Sat, Mar 9, 2013 at 9:54 AM, Eduardo Morras wrote: > > Hello, > > I use cat to read a file and pass it to another app, the command is this: > > camibar% cat file.git | fossil import --git file.fossil > > It takes a lot of time, file.git is 12GB, and i want to know i

Re: How to know % of read file in cat?

El día Saturday, March 09, 2013 a las 10:54:00AM +0100, Eduardo Morras escribió: > > Hello, > > I use cat to read a file and pass it to another app, the command is this: > > camibar% cat file.git | fossil import --git file.fossil > > It takes a lot of time, file.gi

How to know % of read file in cat?

Hello, I use cat to read a file and pass it to another app, the command is this: camibar% cat file.git | fossil import --git file.fossil It takes a lot of time, file.git is 12GB, and i want to know if there's some 'magic' trick can I use to show me how many bytes or the % of t

Re: cat sort(1) sort floating point numbers?

On Monday 03 October 2011 14:05:42 Anton Shterenlikht wrote: > I tried sorting a file with a column of floating > point numbers (below) with sort(1) -n. However, > the numbers seem to have been sorted by the first > digit only. sort -g Due to the GNU project's obsession with info (

cat sort(1) sort floating point numbers?

I tried sorting a file with a column of floating point numbers (below) with sort(1) -n. However, the numbers seem to have been sorted by the first digit only. TZAV> cat numbers 3.895686170464136E-016 6.790214437463702E-003 4.163481430190832E-016 2.224131318975909E-002 4.024567914829249E-

Re: Unexepcted behavior from read and cat

[respecting Time's arrow] On Tuesday 13 May 2008 20:55, Johan Dowdy wrote: > > On 5/12/08 1:55 PM, "RW" <[EMAIL PROTECTED]> wrote: > > > > cat iplist | xargs -n1 dig +short -x > > I think this one wins for brevity. It can be made shorter: http

Re: Unexepcted behavior from read and cat

ead line; dig +short -x `echo $line`; while read line; do dig >> +short -x `echo $line`; done) < iplist >> > I tend to use "xargs -n1" with dig e.g > > > cat iplist | xargs -n1 dig +short -x > > ___ >

Re: Unexepcted behavior from read and cat

On Tuesday 13 May 2008 18:23, Jonathan McKeown wrote: > > The comedy solution: > > lam -s '-x ' trydata | xargs dig +short and of course I meant iplist, not trydata: this was a cut'n'paste, and trydata is my scratch test data filename (often providing input to a script called try. Why isn't it c

Re: Unexepcted behavior from read and cat

On Monday 12 May 2008 20:59, Paul Schmehl wrote: > I created a small list of IPs that I wanted to do digs on (because I'm lazy > and don't want to do them one at a time.) [snip] > WTF? Why do these utilities, which usually read all the lines in a file > now only work once when run through dig? Is

Re: Unexepcted behavior from read and cat

On Mon, May 12, 2008 at 12:22:48PM -0700, Johan Dowdy wrote: > For loops are your friend. > > I'd do something like: > > for i in `cat iplist` > do dig +short -x $I > done Even better: while read i do dig +short -x $i done < iplist See the Useless Use of Cat

Re: Unexepcted behavior from read and cat

ht as well just do them individually. > > > > What am I missing? > > Never mind. > > This worked. > > (read line; dig +short -x `echo $line`; while read line; do dig > +short -x `echo $line`; done) < iplist > I t

Re: Unexepcted behavior from read and cat

For loops are your friend. I'd do something like: for i in `cat iplist` do dig +short -x $I done -J On 5/12/08 11:59 AM, "Paul Schmehl" <[EMAIL PROTECTED]> wrote: > dig +short -x `cat iplist` -- Johan Dowdy - CISSP Senior Systems Administrator nCircle Network

Re: Unexepcted behavior from read and cat

On Monday 12 May 2008, Paul Schmehl wrote: > I created a small list of IPs that I wanted to do digs on (because I'm lazy > and don't want to do them one at a time.) > > I then wrote the following on the commandline: > > % dig +short -x `cat iplist` > > The result

Re: Unexepcted behavior from read and cat

On May 12, 2008, at 11:59 AM, Paul Schmehl wrote: WTF? Why do these utilities, which usually read all the lines in a file now only work once when run through dig? Is there a way to feed dig a list of IPs and have it return each and every one of them? The dig which comes with BIND 9 support

Re: Unexepcted behavior from read and cat

--On Monday, May 12, 2008 13:59:47 -0500 Paul Schmehl <[EMAIL PROTECTED]> wrote: Sure, I can edit the file and prepend +short -x to each line, but by then I might as well just do them individually. What am I missing? Never mind. This worked. (read line; dig +short -x `echo $line`; while rea

Unexepcted behavior from read and cat

I created a small list of IPs that I wanted to do digs on (because I'm lazy and don't want to do them one at a time.) I then wrote the following on the commandline: % dig +short -x `cat iplist` The results was an answer for the first line only. So, I thought read line would do the

Re: /bin/cat: Permission denied

jdow wrote: From: "Viktoras Veitas" <[EMAIL PROTECTED]> Hello. I suddenly cannot run "cat" command as /bin/cat file appears to be without execute permissions (all other files in /bin directory are with them) and I get "/bin/cat: Permission denied" error.

Re: /bin/cat: Permission denied

From: "Viktoras Veitas" <[EMAIL PROTECTED]> Hello. I suddenly cannot run "cat" command as /bin/cat file appears to be without execute permissions (all other files in /bin directory are with them) and I get "/bin/cat: Permission denied" error. I had a misf

/bin/cat: Permission denied

Hello. I suddenly cannot run "cat" command as /bin/cat file appears to be without execute permissions (all other files in /bin directory are with them) and I get "/bin/cat: Permission denied" error. I had a misfortune to "chmod 555 /bin/cat", then my machine pan

Re: cat /proc/cpuinfo ?

:; dmidecode ... Version: Intel(R) Celeron(R) Voltage: 1.5 V External Clock: 130 MHz Max Speed: 3200 MHz Current Speed: 2865 MHz< Status: Populated, Enabled Upgrade: ZIF Socket L1 Cache Handle: 0x0009 L2 Cache Handle: 0

Re: cat /proc/cpuinfo ?

On 27/03/06 Dhénin Jean-Jacques said: > pkg_add cpuid > > and > > :; cpuid > > eax ineax ebx ecx edx > 0002 756e6547 6c65746e 49656e69 > 0001 0f27 0001080a 0400 bfebfbff > 0002 665b5101 003b7040 > 8000 8004

Re: cat /proc/cpuinfo ?

Family, > > > > Yes, yes, I know... I have a bunch of boxes under my desk here at > > home and between the Ultra-10, FreeBSD-5.4 and 6.0 and SuSE I get > > confused and that's what happened when I tried to type the following > > on my FreeBSD box. > > > >

Re: cat /proc/cpuinfo ?

pened when I tried to type the following > on my FreeBSD box. > > cat /proc/cpuinfo > [] > > Is there some *BSD port that will give me CPU information like the > above from the command line? You want the linux /proc behaviour. 1) make sure you have linux binary compati

Re: cat /proc/cpuinfo ?

t; > > Hello Family, > > > > Yes, yes, I know... I have a bunch of boxes under my desk here at > > home and between the Ultra-10, FreeBSD-5.4 and 6.0 and SuSE I get > > confused and that's what happened when I tried to type the following > > on my FreeB

Re: cat /proc/cpuinfo ?

Yep, It is located in your sysctl Try this: ' sysctl -a | less ' That should give you all info about the system including cpu, memory ect.. - Original Message - From: "Bill Schoolcraft" <[EMAIL PROTECTED]> To: Sent: Monday, March 27, 2006 12:47 AM

cat /proc/cpuinfo ?

Hello Family, Yes, yes, I know... I have a bunch of boxes under my desk here at home and between the Ultra-10, FreeBSD-5.4 and 6.0 and SuSE I get confused and that's what happened when I tried to type the following on my FreeBSD box. cat /proc/cpuinfo What I did get off my other box, where

RE: cat /dev/urandom

> shell# cat /dev/urandom > > can that executed as root cause any harm to the system? What > if a random > sequence of `rm *` was generated... would it be executed? > the question is: WHAT FOR should someone logged in as root execute "cat /dev/urandom" without red

Re: cat /dev/urandom

o a pipe. Just typed too soon, and didn't proof, I guess. I hope no harm has been done. For anyone listening don't type `cat /dev/urandom` because the results are, as they say, "undefined," and potentially (although probably remotely) destructive. lane _

Re: cat /dev/urandom

Lane <[EMAIL PROTECTED]> writes: > I think the backticks (and shell variables) actually send the output to a > pipe, not the screen. I don't know why you said either part of that. I didn't imply the latter and AFAIK the former is untrue (unless you ask the shell to send their output to a pipe);

Re: cat /dev/urandom

On Tuesday 26 July 2005 20:03, you wrote: > I don't use backticks, so this'll have the equivalent "$()". > > The command: cat /dev/urandom > is passed to the shell and the shell executes "cat" and sends > the output to the screen without possibility of

Re: cat /dev/urandom

I don't use backticks, so this'll have the equivalent "$()". The command: cat /dev/urandom is passed to the shell and the shell executes "cat" and sends the output to the screen without possibility of executing anything (except the magic stuff recognized by your

Re: cat /dev/urandom

Lane <[EMAIL PROTECTED]> writes: > On Tuesday 26 July 2005 17:35, Michael Beattie wrote: > > On 7/26/05, Matt Juszczak <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > > > Quick question. > > > > > > shell# cat /dev/urandom > &g

Re: cat /dev/urandom

On Tuesday 26 July 2005 18:47, Michael Beattie wrote: > On 7/26/05, Lane <[EMAIL PROTECTED]> wrote: > > On Tuesday 26 July 2005 18:18, Michael Beattie wrote: > > > `cat /dev/urandom` will do just that... it's not also going to run > > > code from within tha

cat /dev/urandom

Tue, Jul 26, 2005 at 6:32 PM Matt Juszczak <[EMAIL PROTECTED]> > Hi all, > > Quick question. > > shell# cat /dev/urandom > > can that executed as root cause any harm to the system? What if a random > sequence of `rm *` was generated... would it be executed? &

Re: cat /dev/urandom

On 7/26/05, Lane <[EMAIL PROTECTED]> wrote: > On Tuesday 26 July 2005 18:18, Michael Beattie wrote: > > `cat /dev/urandom` will do just that... it's not also going to run > > code from within that output. > > > > On 7/26/05, Lane <[EMAIL PROTECTED]>

Re: cat /dev/urandom

On Tuesday 26 July 2005 18:18, Michael Beattie wrote: > `cat /dev/urandom` will do just that... it's not also going to run > code from within that output. > > On 7/26/05, Lane <[EMAIL PROTECTED]> wrote: > > On Tuesday 26 July 2005 17:35, Michael Beattie wrote: &g

Re: cat /dev/urandom

`cat /dev/urandom` will do just that... it's not also going to run code from within that output. On 7/26/05, Lane <[EMAIL PROTECTED]> wrote: > On Tuesday 26 July 2005 17:35, Michael Beattie wrote: > > On 7/26/05, Matt Juszczak <[EMAIL PROTECTED]> wrote: > > >

Re: cat /dev/urandom

On Tuesday 26 July 2005 17:35, Michael Beattie wrote: > On 7/26/05, Matt Juszczak <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Quick question. > > > > shell# cat /dev/urandom > > > > can that executed as root cause any harm to the system? Wh

Re: cat /dev/urandom

On 7/26/05, Matt Juszczak <[EMAIL PROTECTED]> wrote: > Hi all, > > Quick question. > > shell# cat /dev/urandom > > can that executed as root cause any harm to the system? What if a random > sequence of `rm *` was generated... would it be executed? > >

cat /dev/urandom

Hi all, Quick question. shell# cat /dev/urandom can that executed as root cause any harm to the system? What if a random sequence of `rm *` was generated... would it be executed? I tried that to fix my terminal and forgot it might cause damage as root, even if its just being cat'd t

Including xhtml11.cat in SGML_CATALOG_FILES confuses OpenJade

I asked this question over a week ago, but got no answer. I'll give it one more shot. If someone knowns of a better forum for this, please let me know. /usr/local/share/sgml/catalog -> /usr/local/share/sgml/catalog.ports). There's something about xhtml11.cat that makes some of

Including xhtml11.cat in SGML_CATALOG_FILES confuses OpenJade

Hello, textproc/xhtml-11 adds /usr/local/share/xml/xhtml/1.1/xhtml11.cat to /usr/local/share/sgml/catalog.ports, which gets included in my SGML_CATALOG_FILES setting (/usr/local/etc/sgml/catalog -> /usr/local/share/sgml/catalog -> /usr/local/share/sgml/catalog.ports). There's some

Re: Cat a directory

Karlsson Mikael HKI/SOSV wrote: And while we're on the subject of different file types why doesn't ls support coloring of different file types like in Linux. As it would make finding certain files easier by coloring them differently depending on their ending. Try http://www.mandrakelinux.com/en/

Re: Re:Re: Cat a directory

> > > Now, either contribute something or be done with it. > > I contributed a few clear, well-argumented reasons in favor of my position ^^^ wrong reasons > that "cat" should change its default behavior. You, otoh, h

Re: Re:Re: Cat a directory

[it seems I forgot a paragraph] - Original Message - From: "Jerry McAllister" <[EMAIL PROTECTED]> To: "Mark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 4:21 PM Subject: Re: Re:Re: Cat a directory > > I would

Re: Re:Re: Cat a directory

- Original Message - From: "Jerry McAllister" <[EMAIL PROTECTED]> To: "Mark" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 4:21 PM Subject: Re: Re:Re: Cat a directory But nonetheless very illustrative of how the OS

Re: Re:Re: Cat a directory

> > However, the purpose of "cat" is to write the contents of a file to STDOUT. > And yes, in UNIX pretty much everything is considered a file. But that does > not change the fact that people do not experience a directory as a file, and > in their use of language a

Re: Re:Re: Cat a directory

- Original Message - From: "Matthew Hunt" <[EMAIL PROTECTED]> To: "Karlsson Mikael HKI/SOSV" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, September 22, 2003 6:26 PM Subject: Re: Re:Re: Cat a directory > "cat /bin" on Solaris

Re: Re: Cat a directory

> > On Tue, 23 Sep 2003, Karlsson Mikael HKI/SOSV wrote: > [...] > > which are all supported in for example GNU/Linux ls, except 10 and 11, > > but then they have an extra option to put different coloring on files > > with a special ending. So that archives, moviefiles, soundfiles etc. > > have a

Re:Re: Cat a directory

On Tue, 23 Sep 2003, Karlsson Mikael HKI/SOSV wrote: [...] > which are all supported in for example GNU/Linux ls, except 10 and 11, > but then they have an extra option to put different coloring on files > with a special ending. So that archives, moviefiles, soundfiles etc. > have a special color w

Re:Re: Cat a directory

pen-source was started so that the people would have the power to decide what they want and not some money obsessed Gates. But it seems that development on FreeBSD has taken a turn towards dictator reign or maybe always been that way. >> >> Other *NIX systems seem to have done this to t

Re: Cat a directory

"Karlsson Mikael HKI/SOSV" <[EMAIL PROTECTED]> wrote: > So it's better for a newbie to get understandable jibrish from cat > when run on directories then an error message stating that they are > trying to run cat on a directory like ls says when they try to run

Re: Re:Re: Cat a directory

> > Read my first post before reading this thing so you'll be on the right track > > > > >> Other *NIX systems seem to have done this to their cat program so why > >> can't FreeBSD? > > > >See above. FreeBSD has a better view of th

Re: Cat a directory

On Mon, 22 Sep 2003 12:01:15 -0400 Damian Gerow <[EMAIL PROTECTED]> wrote: > Thus spake Chris Pressey ([EMAIL PROTECTED]) [22/09/03 11:54]: > > Also, I believe 'GNU ls', in the ports, supports coloured directory > > listings. > > As does FreeBSD's ls. From 'man 1 ls': > > -G

Re: Re:Re: Cat a directory

On Mon, Sep 22, 2003 at 09:06:00AM +0300, Karlsson Mikael HKI/SOSV wrote: > Try to run for example "cat /bin" in Linux, HP-UX, Solaris and other > *NIXes and I'm 90% certain that they will not show the directory but > an error message saying something. "cat /bin&q

Re: Cat a directory

On Mon, Sep 22, 2003 at 08:54:16AM -0700, Chris Pressey wrote: > Also, I believe 'GNU ls', in the ports, supports coloured directory > listings. Have you tried typing 'ls -G' using the system ls(1) recently? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil.

Re: Cat a directory

Thus spake Chris Pressey ([EMAIL PROTECTED]) [22/09/03 11:54]: > Also, I believe 'GNU ls', in the ports, supports coloured directory > listings. As does FreeBSD's ls. From 'man 1 ls': -G Enable colorized output. This option is equivalent to defining CLICOLOR in the

Re: Cat a directory

On 22 Sep 2003 09:06:00 +0300 "Karlsson Mikael HKI/SOSV" <[EMAIL PROTECTED]> wrote: > [...] > Ruben de Groot wrote (19.9.2003 13:34): > > > >So why don't you for example alias cat to cat -v in your system > >profile and login scripts? This will d

Re: Cat a directory

I hesitate to step into the fray; it appears that the phrase `more heat than light' now applies. But ... >> Says who? cat works fine on binary files. The >> problem you are having is that people are using >> cat to *display* files. "Fixing" that proble

Re:Re:Re: Cat a directory

Read my first post before reading this thing so you'll be on the right track Warren Block wrote (19.9.2003 17:41): > >Says who? cat works fine on binary files. The problem you are having >is that people are using cat to *display* files. "Fixing" that problem >c

Re:Re: Cat a directory

On Thu, 19 Sep 2003, Karlsson Mikael HKI/SOSV wrote: > I personally think that some of these tests should be added to the > real distributable version of cat that comes with FreeBSD cause I > can't be the only one that this bugs. I mean what could a little more > code hurt to

Re: Re: Cat a directory

On Fri, Sep 19, 2003 at 08:27:00AM +0300, Karlsson Mikael HKI/SOSV typed: > OK! I admit that it isn't THE BIGGEST problem for me BUT it is A problem. What > I ment in my last mail was that it is the biggest problem concerning cat. Since > someone always seems to cat a binary file

Re: Re: Cat a directory

On Fri, Sep 19, 2003, Karlsson Mikael HKI/SOSV wrote: >OK! I admit that it isn't THE BIGGEST problem for me BUT it is A problem. What >I ment in my last mail was that it is the biggest problem concerning cat. Since >someone always seems to cat a binary file without having the knowled

Re:Re: Cat a directory

OK! I admit that it isn't THE BIGGEST problem for me BUT it is A problem. What I ment in my last mail was that it is the biggest problem concerning cat. Since someone always seems to cat a binary file without having the knowledge of what it causes. I personally think that some of these

Re: Cat a directory

In the last episode (Sep 18), Karlsson Mikael HKI/SOSV said: > What I just wanted to ask was if it's absolutely necessary for cat to > be able to work on directories. Or if it would be possible to simply > add a check to cat that tests if the "file" being opened is a &g

Cat a directory

I've noticed along time that it's possible to cat a directory. I just don't see the point of it being possible to do so since it only returns jibrish. I know that in Linux for example cat returns an error message like this: cat: mail/: Is a directory. I also noticed that in both Fr

cat get sylpheed-claws 0.9.0 to make on freebsd-5.1

After i run ./configure ...successfully i suppose there were no error messagesi try to run make but the process stops with the following: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/include/glib12 -D_THREAD_SAFE -DLOCALEDIR=\"/usr/local/share/locale\" -g -O2 -c mgutils.c -fPIC -DPIC -o

Re: cat

On Wed, 26 Feb 2003, Tijl Coosemans wrote: > I want to remove CRs from text files so what I did is this: > > cat filename | tr -d '\r' > filename > > However, I often end up with an empty file. Just out of > interest, somebody who knows why that is? This is be

Re: cat

The ultimate answer is that the shell interpets the ">" first, truncating the output file to 0. Quickest way to make a file null bytes long (in sh type shells, not in (t(csh) type): $ >filename In bash (also in ksh I think) you can tell the shell not to clobber an existing file, I think the comma

Re: cat

- Original Message - From: Matthew Seaman <[EMAIL PROTECTED]> Date: Wed, 26 Feb 2003 17:14:56 + To: [EMAIL PROTECTED] Subject: Re: cat > On Wed, Feb 26, 2003 at 05:56:13PM +0100, Tijl Coosemans wrote: > > I want Sip > (Note too the influence of t

Re: cat

- Original Message - From: Shantanu Mahajan <[EMAIL PROTECTED]> Date: Thu, 27 Feb 2003 11:05:27 +0530 To: Tijl Coosemans <[EMAIL PROTECTED]> Subject: Re: cat > +++ Tijl Coosemans [freebsd] [26-02-03 17:56 +0100]: > | I want to remove CRs from text files so what I did is

Re: cat

+++ Tijl Coosemans [freebsd] [26-02-03 17:56 +0100]: | I want to remove CRs from text files so what I did is this: | | cat filename | tr -d '\r' > filename | | However, I often end up with an empty file. Just out of | interest, somebody who know

Re: cat

On 2003-02-26 17:56, Tijl Coosemans <[EMAIL PROTECTED]> wrote: > I want to remove CRs from text files so what I did is this: > > cat filename | tr -d '\r' > filename > > However, I often end up with an empty file. Just out of > interest, somebody who knows w

Re: cat

On Wed, Feb 26, 2003 at 05:56:13PM +0100, Tijl Coosemans wrote: > I want to remove CRs from text files so what I did is this: > > cat filename | tr -d '\r' > filename > > However, I often end up with an empty file. Just out of > interest, somebody who knows why t

Re: cat

> > I want to remove CRs from text files so what I did is this: > > > > cat filename | tr -d '\r' > filename > > It's easier with 'tr' but you can also use vi. # vi text.txt :1,$s/^M//g where ^M means that you need to hit Ctrl-V.

Re: cat

On Wednesday 26 February 2003 18:56, someone, possibly Tijl Coosemans, typed: > I want to remove CRs from text files so what I did is this: > > cat filename | tr -d '\r' > filename > > However, I often end up with an empty file. Just out of > interest, somebody who

Re: cat

On Wed, Feb 26, 2003 at 05:56:13PM +0100, Tijl Coosemans wrote: > I want to remove CRs from text files so what I did is this: > > cat filename | tr -d '\r' > filename > > However, I often end up with an empty file. Just out of > interest, somebody who knows why

cat

I want to remove CRs from text files so what I did is this: cat filename | tr -d '\r' > filename However, I often end up with an empty file. Just out of interest, somebody who knows why that is? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questio

Re: Cat.

Charlie ROOT wrote: Hi. If I will have a command running lets say every 5th hour, how do I typ?? the command is: cat resolv.conf > /etc/resolv.conf The information you are looking for is in the crontab manpage (as someone else pointed out) Although I'd like to point out an alternati

Re: Cat.

# [EMAIL PROTECTED] / 2003-02-14 18:40:50 +0100: > > Hi. > If I will have a command running lets say every 5th hour, how do I typ?? > the command is: > > cat resolv.conf > /etc/resolv.conf see crontab(1) and crontab(5) -- If you cc me or remove the list(s) comple

Cat.

Hi. If I will have a command running lets say every 5th hour, how do I typ?? the command is: cat resolv.conf > /etc/resolv.conf Thanks. // Per To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message