redhat-list Digest, Vol 38, Issue 7

Sat Apr 7 16:08:11 UTC 2007

Magic file

Once upon a time, there was a simple text file named /etc/magic and it 
served a wonderful purpose.   Elegant and easy to modify as well as 
use.  Too elegant.  Too easy.   We musn't have THAT! Now, it's some sort of 
compiled file where the tools needed to extend and modify the file aren't 
on the standard Red Hat distribution.   Does anyone know where those tools 
are and how to obtain them?

At 09:00 AM 4/7/2007, you wrote:

>Send redhat-list mailing list submissions to
>         redhat-list at redhat.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.redhat.com/mailman/listinfo/redhat-list
>or, via email, send a message with subject or body 'help' to
>         redhat-list-request at redhat.com
>
>You can reach the person managing the list at
>         redhat-list-owner at redhat.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of redhat-list digest..."
>
>
>Today's Topics:
>
>    1. Re: cron problem (m.roth2006 at rcn.com)
>    2. Re: cron problem (Ray Van Dolson)
>    3. Re: cron problem (m.roth2006 at rcn.com)
>    4. bdc and qmail-scanner (Lord of Gore)
>    5. Re: Soliciting Opinions Regarding File Systems (Nilesh Bansal)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri,  6 Apr 2007 12:15:53 -0400 (EDT)
>From: <m.roth2006 at rcn.com>
>Subject: Re: cron problem
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <20070406121553.CAB32245 at ms08.lnh.mail.rcn.net>
>Content-Type: text/plain; charset=us-ascii
>
>Barry,
>
> >Date: Fri, 6 Apr 2007 10:41:33 -0500 (CDT)
> >From: Barry Brimer <lists at brimer.org>
> >
> >On Fri, 6 Apr 2007 m.roth2006 at rcn.com wrote:
> >
> >> Ok, folks, I'm going nuts. I've set up a cron job to run a script to 
> back up Oracle. In the crontab entry, I've got it piping stdout and 
> stderr to append to a logfile. It runs late every Thursday night.
> >>
> >> Well, allegedly.
> >>
> >> I find entries in /var/log/cron saying it ran... but there's no 
> backup, and no log. Just this week, I added set -x in the script.
> >>
> >> Nada.
> >>
> >> Any suggestions? Oh, and yes, if I run it manually, it works just 
> fine. The no output log *really* drives me nuts....
> >
> >Any chance that this script is relying on environment variables that are
> >available in your current session, but would not be in the cron execution?
> >Are you sourcing any needed environment in the script?  Is there anything
> >in the email that cron sends to the user who owns the cron job that would
> >give more information?
>
>Setting all the ORACLE* in the script. When I run it manually as Oracle, 
>it's fine, even if I haven't source oraenv. It's running as Oracle's cron 
>job, and...
>
><mark gets irritated, and finally install mutt on the box - all that had 
>been on was mail ("a friendly, comformable...." arrrghghghghgh)>
>
>So, now I read oracle's email....
>Right:
>cron env is /bin/sh; and my backup script has #!/bin/bash as the first 
>line, of course, so that's the shell environment.
>
>/bin/sh: -c: line 1: syntax error near unexpected token `&'
>/bin/sh: -c: line 1: `/home/oracle/dbbackup.sh >> 
>/opt/oracle/backup/backup.log 2>>&1'
>
>So it's a syntax error in the crontab entry... but *why*?
>Ok, just went into Bourne, and it doesn't like 2>>&1. So, a simple 
>question: won't it toast backup.log if I don't do that as an append - that 
>is, if I do 2>&1, instead of 2>>&1?
>
>      mark
>
>
>
>------------------------------
>
>Message: 2
>Date: Fri, 6 Apr 2007 09:30:48 -0700
>From: Ray Van Dolson <rvandolson at esri.com>
>Subject: Re: cron problem
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <20070406163048.GA28313 at esri.com>
>Content-Type: text/plain; charset=us-ascii
>
> > So, now I read oracle's email....
> > Right:
> > cron env is /bin/sh; and my backup script has #!/bin/bash as the first 
> line, of course, so that's the shell environment.
> >
> > /bin/sh: -c: line 1: syntax error near unexpected token `&'
> > /bin/sh: -c: line 1: `/home/oracle/dbbackup.sh >> 
> /opt/oracle/backup/backup.log 2>>&1'
> >
> > So it's a syntax error in the crontab entry... but *why*?
> > Ok, just went into Bourne, and it doesn't like 2>>&1. So, a simple 
> question: won't it toast backup.log if I don't do that as an append - 
> that is, if I do 2>&1, instead of 2>>&1?
>
>I think it should be alright with 2>&1.  You're using >> to append to
>the backup.log previous to that and 2>&1 will just made stderr go to
>stdout...
>
>Give it a try and see.
>
>Ray
>
>
>
>------------------------------
>
>Message: 3
>Date: Fri,  6 Apr 2007 12:34:07 -0400 (EDT)
>From: <m.roth2006 at rcn.com>
>Subject: Re: cron problem
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <20070406123407.CAB40348 at ms08.lnh.mail.rcn.net>
>Content-Type: text/plain; charset=us-ascii
>
> >Date: Fri, 6 Apr 2007 09:30:48 -0700
> >From: Ray Van Dolson <rvandolson at esri.com>
> >
> >> So, now I read oracle's email....
> >> Right:
> >> cron env is /bin/sh; and my backup script has #!/bin/bash as the first 
> line, of course, so that's the shell environment.
> >>
> >> /bin/sh: -c: line 1: syntax error near unexpected token `&'
> >> /bin/sh: -c: line 1: `/home/oracle/dbbackup.sh >> 
> /opt/oracle/backup/backup.log 2>>&1'
> >>
> >> So it's a syntax error in the crontab entry... but *why*?
> >> Ok, just went into Bourne, and it doesn't like 2>>&1. So, a simple 
> question: won't it toast backup.log if I don't do that as an append - 
> that is, if I do 2>&1, instead of 2>>&1?
> >
> >I think it should be alright with 2>&1.  You're using >> to append to
> >the backup.log previous to that and 2>&1 will just made stderr go to
> >stdout...
> >
> >Give it a try and see.
>
>Thanks. I've just edited oracle's crontab, and we'll see what happens. In 
>the meantime, waiting for next week, I think I'll do it manually (once 
>most of the developers have left - this is a test box, btw), and then when 
>it runs next week, I'll see if the log file remains.
>
>If not, not a biggie.
>
>     mark
>
>
>
>------------------------------
>
>Message: 4
>Date: Fri, 06 Apr 2007 19:51:44 +0300
>From: Lord of Gore <lordofgore at logsoftgrup.ro>
>Subject: bdc and qmail-scanner
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <46167AA0.5080804 at logsoftgrup.ro>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I have an old machine with qmail on it. Clamdscan took a very long time
>to scan files and I wanted to change the av scanner. I went for
>bitdefender console. Indeed at a 14MB archive the time was tripled when
>using clam.
>Now... When qmail receives a mail it sends it to qmail scanner that
>parses it and breaks it into a few files in a temporary directory.
>When I send an email containing a virus archived with rar it passes the
>scanner. Clam worked just fine. Now, for the kicky part:
>I tinkered with the qmail-scanner script and changed it to show in
>detail what it was doing and came up with the av scanner being called
>like this:
>
><pathto>bdc --all --arc --mail <pathto>tmpdir. (all means all files, arc
>means to parse archives and mail to treat files as mail)
>
>Its output shows that there isn't any virus. I got around to make a copy
>of the files that emerged after such an operation and issued the *same*
>command and bang: the scanner saw the virus.
>Now of course a few of you will say there must be a difference. Well
>there isn't. I manually modified that script considering that I'm either
>stupid, sick or blind and can't see something. It just doesn't perform
>the same way. Well now I want to resolve the problem but seem to be
>missing a button...
>Any thoughts?
>
>10ks
>
>
>
>------------------------------
>
>Message: 5
>Date: Fri, 6 Apr 2007 22:23:06 -0400
>From: "Nilesh Bansal" <nileshbansal at gmail.com>
>Subject: Re: Soliciting Opinions Regarding File Systems
>To: "General Red Hat Linux discussion list" <redhat-list at redhat.com>
>Message-ID:
>         <f36128690704061923o71a3e4bbia044fbc3d9e55c3b at mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8; format=flowed
>
>So what is the problem with ext3 (except for the limitation on largest
>possible filesystem size). I mean, will I have a difference in read or
>write speed/performance of the two filesystems?
>
>thanks
>Nilesh
>
>On 4/6/07, m.roth2006 at rcn.com <m.roth2006 at rcn.com> wrote:
> > >Date: Fri, 6 Apr 2007 09:58:13 -0500
> > >From: "Jim Canfield" <jcanfield at tshmail.com>
> > >
> > >Sean McGlynn wrote:
> > >>
> > >> We are considering what file system to use for an
> > >> enterprise deployment of Linux.  We're reviewing EXT3,
> > >> Reiser, XFS, and JFS.  The server will deal with a fair
> > >I second XFS.  While it's not an enterprise example - I use
> > <snip>
> > XFS/LVM at
> > >home to store all my DVDs (3-5gig files)and have no problems.
> > >Considering the file system is a very mature and handles large files
> > >well I think it's a no brainer.
> >
> > I've started a home system on Reiser, since that's what the default is 
> with SuSE, and I've been *very* pleased, since my wife's (not old!) m/b 
> looks to be failing (we won't talk about the literal lightening strike on 
> the house, and the older UPS it was on...), but the damn thing freezes, 
> sometimes several times a day, sometimes not for days. I can *not* get 
> her to log off every night, and so she'll have many windows up with OO, 
> kmail, and konqueror, and when it does freeze, the *only* way out is the 
> hardware reset switch. She's lost almost nothing, and all the windows 
> come back up, all documents are recovered, etc.
> >
> > So, take that as a rather severe test of robustness of Reiser.
> >
> >     mark
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
> >
>
>
>--
>Nilesh Bansal.
>http://queens.db.toronto.edu/~nilesh/
>
>
>
>------------------------------
>
>__
>redhat-list mailing list
>Unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/redhat-list
>
>End of redhat-list Digest, Vol 38, Issue 7
>******************************************
>
>
>
>
>--
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.446 / Virus Database: 269.0.0/750 - Release Date: 4/6/2007 
>9:30 PM

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 269.0.0/750 - Release Date: 4/6/2007 9:30 PM