On Thu, 06 Jun 2013 14:01:34 +0800
Ed Greshko wrote:
>When the --logfile=file option is specified append log
> output to the specified file. With the --no-syslog option mcelog
> will never log any‐ thing to the syslog.
>
> So, maybe you can create a modified service to do what you w
On 06/06/13 13:33, Frank Murphy wrote:
> mcelog is now handled, by mcelog.service
>
> You can "cat /var/log/messages | grep mce"
> How could that be made more permanent,
> to get all mce events into
> /var/log/mcelog.
>
> Do people just disable the .service,
> and re-enable the mcelog.cron?
I've
mcelog is now handled, by mcelog.service
You can "cat /var/log/messages | grep mce"
How could that be made more permanent,
to get all mce events into
/var/log/mcelog.
Do people just disable the .service,
and re-enable the mcelog.cron?
--
Regards,
Frank - I check for new mail app. 20min
www.fran
On 05.06.2013 22:13, Joe Zeff wrote:
> On 06/05/2013 12:48 PM, Mateusz Marzantowicz wrote:
>
> I think it's fairly safe to assume that that's what it meant, after
> the fact. If you can verify it, however, you might want to report it
> via Bugzilla as the current form of the message is very mislea
On 05.06.2013 22:13, Joe Zeff wrote:
> On 06/05/2013 12:48 PM, Mateusz Marzantowicz wrote:
>> Now, I know that 1.2GB is too less for fedup to do it's job. After some
>> cleanup on root partition (in my case /var is on /) I was able to
>> upgrade to Fedora 19.
>>
>
> If you remember, how much free s
On 06/05/2013 12:48 PM, Mateusz Marzantowicz wrote:
Now, I know that 1.2GB is too less for fedup to do it's job. After some
cleanup on root partition (in my case /var is on /) I was able to
upgrade to Fedora 19.
If you remember, how much free space did you have when it worked? It
might help
On 04.06.2013 22:23, Reindl Harald wrote:
>
> Am 04.06.2013 22:21, schrieb Mateusz Marzantowicz:
>> On 04.06.2013 22:14, Frank Murphy wrote:
>>> On Tue, 04 Jun 2013 22:07:29 +0200
>>> Mateusz Marzantowicz wrote:
>>> . Now I read I have 1.2G but it failed
because of not having 150M of free spa
On Sun, 02 Jun 2013 18:57:42 +, Beartooth wrote:
> The PC I'm on at the moment, my #2, claims to be running F18 :
[snipperoo]
> Is this normal?? Have I screwed up royally somehow? I went
> through the directions at http://fedoraproject.org/wiki/Upgrading (or so
> I thought). Howe
Dear fellow Fedora users,
I just upgraded from F15 to F17, but it won't boot--says it can't find
the root filesystem, which is on a logical volume in an LVM volume group.
(See boot messages below.) For the record, F15 booted just fine with this
structure.
I know this problem--or at least very si
On 05.06.2013 19:37, Frank Murphy wrote:
> I've had to
> it was getting "cannot open display"
> in the logs
>
> I don't use power-manager.
Only marmot knows what you're doing with Xfce. :)
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options
On Wed, 05 Jun 2013 18:08:08 +, Beartooth wrote:
> On Sun, 02 Jun 2013 22:17:18 -0500, Rex Dieter wrote:
>
>> Looks like you've somehow installed a f18 kernel on a genuine f17 box.
>
> That could be :
>
> [btth@Hbsk2 ~]$ cat /etc/fedora-release Fedora release 17 (Beefy
> Miracle)
>
On Wed, 5 Jun 2013 14:00:49 +0100
Frank Murphy wrote:
> from logwatch:
> yumser.frankly3d.home:/lists72G 7.3G
> 64G 11% /lists
>
> The yumser share is 1T
>
> Why does logwatch on the client say 72G
Seemingly it happens if you share under / on the server.
So umount
On Sun, 02 Jun 2013 22:17:18 -0500, Rex Dieter wrote:
> Looks like you've somehow installed a f18 kernel on a genuine f17 box.
That could be :
[btth@Hbsk2 ~]$ cat /etc/fedora-release
Fedora release 17 (Beefy Miracle)
So I played around with rpm and yum doing the things usually
On Wed, 05 Jun 2013 19:29:31 +0200
poma wrote:
xset: line 4: export: `:0.0': not a valid identifier
> >
> > It appears to be the correct display going by:
> > echo $DISPLAY
> > :0.0
>
> Is it really necessary to specify the DISPLAY environment variable
> within "Application Autostart" *.desktop
On 05.06.2013 16:21, Frank Murphy wrote:
> Have the following in xfce autostart:
>
> #!/bin/bash
>
> # Disable screensaver and dpms emergy star.
> export DISPLAY :0.0
> xset s off && \
> xset -dpms
>
> on running:
> ./xset
> ./xset: line 4: export: `:0.0': not a valid identifier
>
> It appear
Our LAN has a mix of Linux and OSX computers connected to it. The Linux
computers work as expected but the OSX computers will not connect,
complains:
"Could not connect to the server because the name or password is not
correct."
The servers contain:
-bash-4.1$ cat /etc/exports
#
#/et
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/05/2013 11:21 AM, William Mattison wrote:
>
>> You might want to open a bugzilla with Xerox to fix the way they build
>> their libraries, with PIC flags.
>
> Done. The second line engineer gave me the sense that it's very unlikely
> that they
> You might want to open a bugzilla with Xerox to fix the way they build their
> libraries, with PIC flags.
Done. The second line engineer gave me the sense that it's very unlikely that
they will implement the requested fix. He said that Fedora and Redhat each
account for less than 0.1% of t
On 06/05/13 22:21, Frank Murphy wrote:
> Have the following in xfce autostart:
>
> #!/bin/bash
>
> # Disable screensaver and dpms emergy star.
> export DISPLAY :0.0
> xset s off && \
> xset -dpms
>
> on running:
> ./xset
> ./xset: line 4: export: `:0.0': not a valid identifier
>
> It appears to b
Have the following in xfce autostart:
#!/bin/bash
# Disable screensaver and dpms emergy star.
export DISPLAY :0.0
xset s off && \
xset -dpms
on running:
./xset
./xset: line 4: export: `:0.0': not a valid identifier
It appears to be the correct display going by:
echo $DISPLAY
:0.0
--
Regar
On Tue, Jun 4, 2013 at 1:22 PM, Martin Airs wrote:
> On Tuesday 04 Jun 2013 22:07:29 Mateusz Marzantowicz wrote:
>>
>> I can't. Disk layout is fixed (but if all fails, I can try to mount
>> /var/cache/yum on some USB disk). I'm doing massive cleanup now on my /
>> (root).
>>
>> This still does not
Am 05.06.2013 12:45, schrieb Gary Stainburn:
> I've still got a number of old F9 systems that are still doing a sturdy job
> (and I don't have time to upgrade).
hopefully the are not connected to the internet!
> However, one of them has got a broken yum setup. Every time I try to do any
> upd
Am 04.06.2013 22:21, schrieb Mateusz Marzantowicz:
> On 04.06.2013 22:14, Frank Murphy wrote:
>> On Tue, 04 Jun 2013 22:07:29 +0200
>> Mateusz Marzantowicz wrote:
>> . Now I read I have 1.2G but it failed
>>> because of not having 150M of free space.
>>>
>>>
>> You might have but did you
>> "df
On Tue, Jun 4, 2013 at 6:56 PM, Peter Gueckel wrote:
> Richard Shaw wrote:
>
> > RPM Fusion generally follows the Fedora guidelines, which include
> > when and when not to update, so 1.0.X to 1.1.X would generally be
> > discouraged within a release.
>
> I asked on their mailing list during rough
from logwatch:
yumser.frankly3d.home:/lists72G 7.3G
64G 11% /lists
The yumser share is 1T
Why does logwatch on the client say 72G
--
Regards,
Frank - I check for new mail app. 20min
www.frankly3d.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscrib
Hi folks.
I've still got a number of old F9 systems that are still doing a sturdy job
(and I don't have time to upgrade).
However, one of them has got a broken yum setup. Every time I try to do any
updates etc. I get the following. I've tried 'yum clean all' but that hasn't
helped.
Any ideas
On 05/22/2013 05:31 AM, Garry T. Williams wrote:
Backlight control is not working, but I developed a very simple
work-around that re-enables it under Fedora.
Oddly, I do not see that bug under GNOME. Backlight controls work fine
for me with an unmodified configuration.
I installed the KDE
27 matches
Mail list logo
