On Wed, 6 Aug 2014 22:20:20 -0700
John Jason Jordan dijo:
>OK, I am booted to the Xubuntu 14.04.1 live DVD. I shows icons on the
>desktop for the various drives and I mounted the one where the OS is
>located (sdb1). With the file manager I can see the /boot folder. And I
>know for certain that th
I'll bite. So far I've heard: "Horrible MongoDB is better than horrible
CouchDB and PostgreSQL JSON extensions are now as fast as the hipster
JSON DB's.
Given that the project as a very brief window to change direction, what
would you recommend and what replicated solution are there people who
ca
OK, I am booted to the Xubuntu 14.04.1 live DVD. I shows icons on the
desktop for the various drives and I mounted the one where the OS is
located (sdb1). With the file manager I can see the /boot folder. And I
know for certain that this is the right drive and partition because a
long time ago Keit
Try not to swallow the whole thing, take it in steps, for example, you
need the get the computer booted before you can fix it, work on that.
Instructions for that are in the post.
On 08/06/2014 09:32 PM, John Jason Jordan wrote:
> On Wed, 6 Aug 2014 20:59:38 -0700
> Jeff Kirsher dijo:
>
>> http:
Simply put, the guide in the thread Jeff pointed too will run the
commands that I mentioned, and a few others, for you.
It's the path to take it you are in a hurry, don't want to make a
mistake, and aren't sure you want to dive in to doing it manually just yet.
The result should be identical. Its
On Wed, 6 Aug 2014 20:59:38 -0700
Jeff Kirsher dijo:
>http://ubuntuforums.org/showthread.php?t=2218362
This may have the answer, but I don't understand very much of it.
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/li
On Wed, 06 Aug 2014 20:56:12 -0700
Ben Koenig dijo:
>You've got to boot off the 14.04 disc...
>chroot into your root partition ( MOUNT it wooo boy!)
>run 'update-grub'
>a 'grub-install /dev/sdX' may also be necessary, but its hard to say.
>you could do it for safety. replace sdX with your parti
HA! Trying to ruin my fun are you! No one will ever learn if they always
take the easy road.
Although, admittedly, that command wraps up most of what I said in a
single command!
I guess I enjoy the thrill of manually executing my bootloader >.<
On 08/06/2014 08:59 PM, Jeff Kirsher wrote:
> http
http://ubuntuforums.org/showthread.php?t=2218362
On Wed, Aug 6, 2014 at 8:25 PM, John Jason Jordan wrote:
> I finally decided I had no choice but to upgrade my Xubuntu 13.10
> laptop to 14.04, so I did so just now. On restarting I get:
>
> error: symbol 'grub_term_highlight_color' not found.
> E
You've got to boot off the 14.04 disc...
chroot into your root partition ( MOUNT it wooo boy!)
run 'update-grub'
a 'grub-install /dev/sdX' may also be necessary, but its hard to say.
you could do it for safety. replace sdX with your partition/MBR
Have fun. This is what happens when you upgrade U
Rich Shepard wrote:
# The 'Service' option expects either the name of a filter
# (in/usr/share/logwatch/scripts/services/*) or 'All'.
# The default service(s) to report on. This should be left as All for
# most people.
Service = All
# You can also disable certain services (when specifying all)
Se
I finally decided I had no choice but to upgrade my Xubuntu 13.10
laptop to 14.04, so I did so just now. On restarting I get:
error: symbol 'grub_term_highlight_color' not found.
Entering rescue mode...
grub rescue>
I have no idea what to do now, but I get pretty desperate when my main
computer i
Speaking of wusses, or the opposite, in this case. Use your Launch Loop (
https://en.wikipedia.org/wiki/Launch_loop ), if you have one, to orbit over
to our own anti-wuss' wikipedia page:
https://en.wikipedia.org/wiki/Keith_Lofstrom
Happy Anniversary Keith
On Wed, Aug 6, 2014 at 6:11 PM, Keith
August 6 2012, Sunday night at 10 pm, two auditoriums at OMSI were
jammed with (1000?) people watching the live feed from JPL of the
landing of the Mars Science Laboratory in Gale crater. Yells,
whoopie, hugs, pandemonium!
Brought to you by Linux. Jet Propulsion Laboratory has vast
compute resou
On 2014-08-06 15:13, Michael Dexter wrote:
> I am in urgent need for someone with (actual) MongoDB replication
> experience.
I am so very sorry.
> Can you help?
Thermite. A deep hole for the remains. A stake through the CPU.
I've worked with replicated MongoDB in the past, I'd normally only
Hello all,
I am in urgent need for someone with (actual) MongoDB replication
experience.
Can you help?
Michael Dexter
PLUG Volunteer
___
PLUG mailing list
PLUG@lists.pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On Wed, 6 Aug 2014, Eric Wilhelm wrote:
> If you're getting no error output and not the expected results, you might
> look for unchecked exit code on system() or backtick/qx{}. Those bits
> might also be in your strace output. `grep sendmail`?
Eric,
Nice thought. Here's what I find:
$ grep s
# from Rich Shepard on Wednesday 06 August 2014:
> However, ... running 'logwatch.pl --output stdout' does display the
>report on the console, so the problem seems to be back to an issue
>with sendmail rather than logwatch.pl. Yet, a few days ago the
>problem was the opposite: changing logwatch.c
Rich Shepard wrote:
> On Wed, 6 Aug 2014, Dale Snell wrote:
>
>> ENOTTY is an error; one could translate it as "Error: No Terminal". At a
>> guess, logwatch tried to open a device or file as a target to recieve its
>> standard output, and failed. Why, I do not know. It's going to take some
>> more
On Wed, 6 Aug 2014, Michael Rasmussen wrote:
> What are the parameters you normally call logwatch.pl with?
It runs from /etc/cron.daily/0logwatch which is a soft link to
/usr/share/logwatch/scripts/logwatch.pl. The configuration is in
/usr/share/logwatch/default.conf/logwatch.conf:
##
On Wed, Aug 06, 2014 at 11:44:19AM -0700, Rich Shepard wrote:
> On Wed, 6 Aug 2014, Rich Shepard wrote:
>
> > With the debug option nothing indicative of a problem shows up.
>
>However, ... running 'logwatch.pl --output stdout' does display the report
> on the console,
What are the parame
On Wed, 6 Aug 2014, Dale Snell wrote:
> ENOTTY is an error; one could translate it as "Error: No Terminal". At a
> guess, logwatch tried to open a device or file as a target to recieve its
> standard output, and failed. Why, I do not know. It's going to take some
> more troubleshooting, I'm afraid
On Wed, 6 Aug 2014 11:35:27 -0700 (PDT)
Rich Shepard wrote:
> On Wed, 6 Aug 2014, Dale Snell wrote:
>
> > Try running the strace output file through grep, looking for the
> > string "ERR" or "ENO". It's a long shot, but it can't hurt to
> > try.
>
> Dale,
>
>No errors, but some ENOTTY; do
On Wed, 6 Aug 2014, Rich Shepard wrote:
> With the debug option nothing indicative of a problem shows up.
However, ... running 'logwatch.pl --output stdout' does display the report
on the console, so the problem seems to be back to an issue with sendmail
rather than logwatch.pl. Yet, a few d
On Wed, 6 Aug 2014, Dale Snell wrote:
> Try running the strace output file through grep, looking for the
> string "ERR" or "ENO". It's a long shot, but it can't hurt to
> try.
Dale,
No errors, but some ENOTTY; don't know if those are new or were always
there.
> What options did you specify
Portland Linux/Unix Group General Meeting Announcement
Who: Beth 'pidge' Flanagan
What: Open Sourcing the Modern Battle Rifle: Legal and technical
implications in home building the semi-automatic AK-47
Where: PSU, 1930 SW 4th Ave. Room FAB 86-01 (Lower Level)
When: Thursday, August 7th, 2014 at 7p
On Wed, 6 Aug 2014 07:39:16 -0700 (PDT)
Rich Shepard wrote:
>After changing logwatch.pl to send its reports by mail the script
> worked for a few days. Today it failed completely. That is, running
> from the command line produces no output in the virtual terminal so
> apparently there's nothi
On Wed, 6 Aug 2014, Michael Rasmussen wrote:
Michael,
> use strict;
Yes.
> use warnings;
No.
> If not add them and forward the output after you run it again.
No output to console or mail.
> And forward a copy to me off list.
logwatch-strace.log sent separately and gzipped.
Tha
are:
use strict;
use warnings;
at the top?
If not add them and forward the output after you run it again.
And forward a copy to me off list.
On Wed, Aug 06, 2014 at 07:39:16AM -0700, Rich Shepard wrote:
>After changing logwatch.pl to send its reports by mail the script worked
> for a few da
After changing logwatch.pl to send its reports by mail the script worked
for a few days. Today it failed completely. That is, running from the
command line produces no output in the virtual terminal so apparently
there's nothing to report via mail either.
Running logwatch.pl via strace produ
30 matches
Mail list logo
