Mail log problem -
by Bob Goodwin
I had been using Mail -s "msg-logs" bobgoodwin(a)wildblue.net <
/var/spool/mail/bobg
until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these
messages not to go through since it appeared to me that they were making
changes that created a lot of disruption in the mail server operation at
that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin(a)wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a
Thunderbird directory "msg-logs" The filter set up looks ok. I haven't
changed anything there and if it didn't work I would hope the mail would
just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is
actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've
been putting this problem off but it's an annoyance that needs fixing!
Bob Goodwin
17 years
Re: Network Places
by Michael McGillick
Thank you.
----- Original Message ----
From: Arthur Pemberton <pemboa(a)gmail.com>
To: For users of Fedora <fedora-list(a)redhat.com>
Sent: Thursday, June 28, 2007 12:59:06 PM
Subject: Re: Network Places
On 6/28/07, Michael McGillick <michael_mcgillick(a)yahoo.com> wrote:
>
> Hi:
>
> Windows Vista offers a concept called a network place that lets me map a Web
> address to a folder. When I open the folder, I'm prompted for a username and
> password, but can then use the folder just like any other folder on my local
> system. Does anyone know if Fedora 7 or Linux itself offers a feature
> similar to this? Thanks.
This has been here at least since Windows 95. KDE has something
similar which I at least consider to be better.
>
> - Michael
> --
> fedora-list mailing list
> fedora-list(a)redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list
>
--
Fedora Core 6 and proud
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
17 years
Help needed with hanging bash script
by Matthew J. Roth
Bash gurus,
I have a bash script that monitors a directory for files. Whenever it
finds files in this directory, it passes them to a support script for
processing. The support script moves the files to another directory
prior to processing them, and it is run in the background to prevent
blocking the main script. A simplified version of the main script loop
follows:
# Execute once every 10 seconds
while true;
do
# Fork a background script to process each file in the spool directory
for fname in `ls /spool/dir/*.ext 2> /dev/null`
do
bname=`basename $fname`
bg_script $bname &
done
sleep 10
done
This is pretty simple and it worked flawlessly for over a year on a dual
processor server running Fedora Core 3. However, after upgrading to an
8 core (2 CPUs x 4 cores) server running Fedora Core 6 the script hangs
a few times a week. This is a bad thing, so I have to keep a close eye
on the server until the bug is resolved.
The process tree of the script when it's hanging follows:
[root@server ~]# ps axjf
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
1 3512 3510 2302 ? -1 S 0 0:59 /bin/bash
/usr/local/bin/script
3512 21432 3510 2302 ? -1 R 0 40:50 \_ /bin/bash
/usr/local/bin/script
Note that the parent process (PID 3512) is sleeping and has accumulated
relatively little CPU time since boot. The child process (PID 21432) is
running in a hard loop and top shows that it is consuming 100% of one of
the cores. It also never terminates, so it permanently blocks the
parent process. If the child process is killed, the execution of the
parent process restarts without any problems.
The interesting thing is that the script never calls itself. It only
calls the support script as a background job. I'm not an expert on the
inner workings of bash, but I believe that the child process is a
temporary artifact of the fork-exec call sequence used to run the
commands in the parent. It seems that a copy of the existing process is
created, but it is never overwritten with the child process.
I researched the logs and I'm fairly confident that the script is
hanging at the top of the for loop, presumably after exhausting the list
created by the "ls" command. There is nothing interesting about the
"ls" command itself, as there are usually less than 20 files in the
directory it's listing.
I'd appreciate any replies from anyone who has experienced this
problem. I have some ideas for working around it, but I'd like to
actually understand its cause and how to properly resolve it so that I
don't get stuck on something similar in the future.
Thank you,
Matthew Roth
InterMedia Marketing Solutions
Software Engineer and Systems Developer
17 years
[F7] Most reliable RAID level
by Chris Tyler
On Wed, 27 Jun 2007 15:06:31 +0200 Stuart Murray-Smith wrote:
>
> What is the preferred/most reliable level to implement software RAID
> on a Fedora 7 server?
Some thoughts to add to what has already been said:
- Raid 1 is expensive on a cost-per-gigabyte basis. Although it's
usually used in a two-bank configuration, there is no reason why you
have to stop at two copies of your data -- you could have three or four
copies if you wanted. If the disks are on separate controllers, you can
read and write them in parallel, yielding good performance (1x write, Nx
read).
- Raid 5 provides a good cost-per-gigabyte, because only one drive is
storing redundant information for each stripe. The write performance is
worse than raid-1 and worse than a single drive, but the read
performance is somewhere between a single drive and raid-1 (you can read
in parallel, but not every drive has every block).
- Raid 6 is like raid 5 with extra paranoia.
But in all of this, a few things to consider:
- You'll want to use software raid managed by the kernel in all but the
most extreme cases (where it may make sense to use hardware raid). The
CPU overhead is minimal on a modern system. Avoid motherboard raid,
since it is in most cases a type of software raid that's tied to the
motherboard BIOS. Using the kernel raid facilities gives you maximum
flexibility in the case of a hardware failure (and resulting crisis):
you won't need a source a particular motherboard model and software
version or a special disk controller to recover your data.
- If you're really paranoid, buy different brands or at least different
batches of disks. There have been cases where several disks of the same
brand fail within a very short time of each other (see for example
http://tinyurl.com/34rrlo ) which can lead to irrecoverable data loss.
- Hot spares enable a drive array to be rebuilt without your
intervention.
- Don't forget power supplies and controllers as possible points of
failure. Power supplies are particularly bad because a failure can take
out multiple drives plus the controller(s).
- Obviously raid is no substitute for backup, because it doesn't protect
against lightning strikes, fire, server theft, data corruption due to
bugs, or user stupidity.
--
Chris Tyler
http://dailypackage.fedorabook.com
17 years
Sata controler using ata driver?
by John Bowden
Hi list
My new 250Gb SATA drive is making a clicking noise from time to time, starting
approximately 10 minuets or so from boot up. I just fired up the hardware
browser and its telling me its using ata_generic driver for a nVida mcp61
chip. Is this normal?
--
Guy Fawkes, the only man to enter the house's of Parliament
with honest intentions, (he was going to blow them up!)
Registered Linux user number 414240
17 years
Red Hat 6 - FC6
by Karl Larsen
I have been thinking that fstab has changed some but right now it is
the same as the older one in Red Hat version 6 (RH6). All the basics of
Unix are still here in Fedora Core 6 and onto Fedora 7.
It is possible to use LABEL rather than actual partition designator
such as /dev/hdb3. Some think the LABEL makes it easier but I am not one.
When I decided to change fstab and grub.conf to remove the LABEL and
instead use the actual designator but I did it in small steps worried
that such a change could make my system un-bootable. But no problems
were found and now I have a lot of lines in fstab letting me as myself
to mount old linux and Windows to this system. It has all worked to this
time.
All of this was possible on RH6 about 10 years ago. Sure is nice FC6
can still do this :-)
Karl
17 years
F7 and Xen and SELINUX clarification
by Mark Haney
I just upgrade to f7 and wanted to use xen to build a couple of vms to
have as test boxes. Unfortunately every time I build a F7 guest it
refuses to boot correctly hanging on selinux testing the usbfs, I read
in the Docs this about SELINUX:
The SELinux policy in Fedora 7 has the neccessary rules to allow use of
Xen with SELinux enabled. The main caveat to be aware of is that any
file backed disk images need to be in a special directory -
/var/lib/xen/images. This applies both to regular disk images, and ISO
images. Block device backed disks are already labelled correctly to
allow them to pass SELinux checks.
So, if I create a 10GB file for the image of the guest I'm building, I
/must/ put it in /var/lib/xen/images? Is that how this reads?
--
Da mihi sis bubulae frustrum assae, solana tuberosa in modo gallico
fricta, ac quassum lactatum coagulatum crassum
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
Call (866) ERC-7110 for after hours support
17 years
Headless Fedora?
by Montana Quiring
Hello,
I would like to setup a headless Fedora box (i.e. No X).
Is there an install parameter or respin I can use to accomplish this,
or should I not bother?
Thanks in advance for your reply.
-Montana
17 years
mediawiki 1.9.2 -- no mediawiki.conf
by Michael Semcheski
Hello,
I just setup a Fedora 7 system from scratch, and everything has been
great. I want it to run mediawiki, so I was really glad to see that
as a package that could be installed via pirut.
I checked it off, and there were no errors in the installation.
That's about as far as I've gotten. It created files in:
/usr/lib/mediawiki
/usr/share/mediawiki
/usr/share/doc/mediawiki
/var/www/wiki
I was expecting /etc/httpd/conf.d/mediawiki.conf, but according to
`rpm -ql mediawiki` there is nothing besides files in the directories
I mentioned above.
Two other notes: I have postgres installed, but not mysql. I'm fine
with either one being used for the wiki.
I was expecting to install it from source anyway, so I'm ok with going
that route, but it would be nice to have the updates handled by yum
and not me. Anyone have any suggestions? Is there something I
missed?
Thanks,
Mike
17 years