On Tue, 27 Aug 2019 at 23:40, Philip Rhoades wrote:
> Tony,
>
>
> On 2019-08-28 07:09, Tony Nelson wrote:
> > On 19-08-27 08:07:17, Philip Rhoades wrote:
> >> People,
> >>
> >> ...there is a consistent "SERVICE_STOP pid=1 uid=0" command that
> >> occurs but I don't know if that is normal or not .
Tony,
On 2019-08-28 07:09, Tony Nelson wrote:
On 19-08-27 08:07:17, Philip Rhoades wrote:
People,
...there is a consistent "SERVICE_STOP pid=1 uid=0" command that
occurs but I don't know if that is normal or not . .
...
That just means that systemd (pid 1) did something that auditd
report
On 19-08-27 08:07:17, Philip Rhoades wrote:
People,
...there is a consistent "SERVICE_STOP pid=1 uid=0" command that
occurs but I don't know if that is normal or not . .
...
That just means that systemd (pid 1) did something that auditd
reported. There are lots of them. E.g., your:
Aug 9
last six /var/log/messages file just prior
to the hang - there is a consistent "SERVICE_STOP pid=1 uid=0" command
that occurs but I don't know if that is normal or not . .
Any suggestions about further debugging would be greatly appreciated!
Regards,
Phil.
Aug 9 22:00:45 loc
On 04/24/2017 03:22 AM, M. Fioretti wrote:
I DO remember that I created an empty esmtprc, for testing, and
then when restarted crond would complain that:
"Local delivery not possible without a MDA"
Right. If you wanted local delivery, you'd probably install the
"esmtp-local-delivery" rpm.
On 2017-04-21 08:59, M. Fioretti wrote:
Greetings,
a few minutes ago, I realized that, on a Fedora 25 box I have...
- my /var/log/messages was almost 15 MILLIONS lines long.
- 99% of those lines (~20/second) are like this:
crond: No configuration file found at /home/marco/.esmtprc or
/etc
On 04/21/2017 10:03 AM, Rick Stevens wrote:
That's odd as cron only checks its tables once a minute. It's almost as
if there's a script in a loop with a "sleep 20" or something akin to it
inside the loop or a program doing the same.
I read 20/second as 20 times per second.
It's interesting th
On 04/21/2017 03:15 PM, Cameron Simpson wrote:
2: What uses estmp?
esmtp will provide /usr/sbin/sendmail if it's the only MTA installed, in
which case cronie will use it to deliver job output.
___
users mailing list -- users@lists.fedoraproject.o
On 04/20/2017 11:59 PM, M. Fioretti wrote:
crond: No configuration file found at /home/marco/.esmtprc or
/etc/esmtprc
but the only line in my own crontab is a shell script that runs every
minute. When I run that script manually, from the command line, it
yelds no error or warning.
At thi
On 04/20/2017 11:59 PM, M. Fioretti wrote:
> Greetings,
>
> a few minutes ago, I realized that, on a Fedora 25 box I have...
>
> - my /var/log/messages was almost 15 MILLIONS lines long.
> - 99% of those lines (~20/second) are like this:
>
> crond: No configuration f
On Fri, 21 Apr 2017 08:59:17 +0200
"M. Fioretti" wrote:
> Greetings,
>
> a few minutes ago, I realized that, on a Fedora 25 box I have...
>
> - my /var/log/messages was almost 15 MILLIONS lines long.
> - 99% of those lines (~20/second) are like this:
>
>
On 21Apr2017 08:59, M. Fioretti wrote:
a few minutes ago, I realized that, on a Fedora 25 box I have...
- my /var/log/messages was almost 15 MILLIONS lines long.
- 99% of those lines (~20/second) are like this:
crond: No configuration file found at /home/marco/.esmtprc or
/etc/esmtprc
but
Greetings,
a few minutes ago, I realized that, on a Fedora 25 box I have...
- my /var/log/messages was almost 15 MILLIONS lines long.
- 99% of those lines (~20/second) are like this:
crond: No configuration file found at /home/marco/.esmtprc or
/etc/esmtprc
but the only line in my own
My /var/log/messages log is full of this error
Jan 7 10:59:49 laptop kernel: hub 4-5:1.0: hub_ext_port_status failed
(err = -32)
Jan 7 10:59:49 laptop kernel: hub 4-5:1.0: hub_ext_port_status failed
(err = -32)
Jan 7 10:59:49 laptop kernel: hub 4-5:1.0: hub_ext_port_status failed
(err
On 04/29/2014 04:56 PM, Chris Kottaridis wrote:
Actually rsyslog is what I needed. Enabled and started it and rebooted
and now I see messages and mailog.
I don't remember having to do that in F19, but maybe I made slightly
different installation choices.
Thanks
You're welcome. It is a change
Actually rsyslog is what I needed. Enabled and started it and rebooted
and now I see messages and mailog.
I don't remember having to do that in F19, but maybe I made slightly
different installation choices.
Thanks
Chris Kottaridis
On 04/29/2014 03:12 PM, Dr. Michael J. Chudobiak wrote:
On 04
On 04/29/2014 03:59 PM, Chris Kottaridis wrote:
I am migrating from a Fedora 19 to a Fedora 20 host. I used the Fedora
20 live disk to install on the new machine. I have most things
transferred over and working, but curiously I don't have any messages or
mail log files in /var/log as I do in the
I am migrating from a Fedora 19 to a Fedora 20 host. I used the Fedora
20 live disk to install on the new machine. I have most things
transferred over and working, but curiously I don't have any messages or
mail log files in /var/log as I do in the F19 host:
# ls /var/log
anaconda dnf.rpm.log
disk usage, and you can
adjust the configuration of logrotate to get rid of the log files
sooner. When partitions/disks are more than 50% full, start planning to
extend the storage capacity.
For comparison, /var/log/messages currently goes over six days here and is
344kB in size.
--
Fedora
OK,
I run fine,
Thus I deleted some big files.
recover some room on the /
/dev/sdb6 6192704 5216872 661260 89% /
but then again:
/dev/sdb6 6192704 5532276 345856 95% /
I guess that it is the /var which grows up to fast!
I have /usr /t
"Patrick Dupre" writes:
> Hello,
>
> I have a /var/log/messages file of size: 74197292
> Is it resonable?
That depends on what´s in it. Under some circumstances, there can be
quite a bit of logging going on.
Logrotate is supposed to deal with it and might not have
On Fri, 07 Mar 2014 12:24:09 +0100
"Patrick Dupre" wrote:
> OK,
>
> Can I force it?
> logrotate -f /etc/logrotate.conf
>
> did not help.
>
ls -l /var/log/messages
___
Regards
Frank
frankly3d.com
--
users mailing list
users@lists.fedoraproject.org
To uns
OK,
Can I force it?
logrotate -f /etc/logrotate.conf
did not help.
> On Fri, 07 Mar 2014 02:34:20 +0100
> Patrick Dupre wrote:
>
> > I have a /var/log/messages file of size: 74197292
> > Is it resonable?
>
> Probably not. Is logrotate turned off or not ins
On Fri, 07 Mar 2014 02:34:20 +0100
Patrick Dupre wrote:
> I have a /var/log/messages file of size: 74197292
> Is it resonable?
Probably not. Is logrotate turned off or not installed?
Here's my logs:
zooty> ls -l /var/log/messages*
-rw--- 1 root root 289231 Mar 6 19:59 /va
Hello,
I have a /var/log/messages file of size: 74197292
Is it resonable?
Thank.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Universi
On Wed, 01 May 2013 12:22:18 +0200
Reindl Harald wrote:
> Normally you simply type "> /var/log/messages" which finally
> mean "redirect nothing to the file" and since append would
> be >> it is cleared
>
Thank you Harald,
I'm still lea
Am 01.05.2013 09:52, schrieb Frank Murphy:
> How to safely clean /var/log/messages for specific testing.
> or set it to hourly rotate.
> Couldn't see specific config in /etc/logrotate.d
logotate does not work this way
/etc/logrotate.d/syslog
/var/lib/logrotate.status
> Have
On Wed, 01 May 2013 11:20:15 +0200
Jon Ingason wrote:
> Have you looked in /etc/logrotate.d/syslog?
>
> On my F18 it contains:
>
> $ more /etc/logrotate.d/syslog
> /var/log/messages
Missed it,
Will separate message from it,
put it in it own conf and hope it keeps.
2013-05-01 09:52, Frank Murphy skrev:
How to safely clean /var/log/messages for specific testing.
or set it to hourly rotate.
Couldn't see specific config in /etc/logrotate.d
Have tried "logrotate --force /var/log/messages"
lots of "error: /var/log/messages:7137 unknown opti
On 05/01/2013 12:52 AM, Frank Murphy wrote:
How to safely clean /var/log/messages for specific testing.
or set it to hourly rotate.
Couldn't see specific config in /etc/logrotate.d
Have tried "logrotate --force /var/log/messages"
lots of "error: /var/log/messages:7137
How to safely clean /var/log/messages for specific testing.
or set it to hourly rotate.
Couldn't see specific config in /etc/logrotate.d
Have tried "logrotate --force /var/log/messages"
lots of "error: /var/log/messages:7137 unknown option 'May' --
ignoring line&
Around 09:11pm on Friday, April 05, 2013 (UK time), Rick Stevens scrawled:
> Make sure your mountd daemon has been updated. Also, if that machine
> isn't an NFS server, disable mountd:
>
> systemctl stop nfs-mountd.service
> systemctl disable nfs-mountd.service
Thanks. This isn't a n
On 04/05/2013 09:47 AM, Steve Searle issued this missive:
On three or four occasions now on one of my Fedora 18 machines warns
that I am running out of space on /var (it has its own partition). This
is due to /var/log/messages being full of rpc.statd[1282]: my_svc_run()
- select: Bad file
On three or four occasions now on one of my Fedora 18 machines warns
that I am running out of space on /var (it has its own partition). This
is due to /var/log/messages being full of rpc.statd[1282]: my_svc_run()
- select: Bad file descriptor messages - these are repeated many times a
second
with these messages:
Apr 2 07:49:01 nbecker1 dbus-daemon[977]: ** (upowerd:1198): WARNING **:
Property get or set does not have an interface string as first arg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/ma
On 02/19/2012 09:03 PM, Tom Horsley wrote:
On Sun, 19 Feb 2012 18:56:57 -0500
Lester M Petrie wrote:
Hi
The following 2 lines are repeated every 30 secs in /var/log/messages.
What causes them, or more importantly, how can I stop them. This is a
desktop machine running Fedora 16.
Fixing the
On Sun, 19 Feb 2012 18:56:57 -0500
Lester M Petrie wrote:
> Hi
>
> The following 2 lines are repeated every 30 secs in /var/log/messages.
> What causes them, or more importantly, how can I stop them. This is a
> desktop machine running Fedora 16.
Fixing the source of the mes
Hi
The following 2 lines are repeated every 30 secs in /var/log/messages.
What causes them, or more importantly, how can I stop them. This is a
desktop machine running Fedora 16.
uname -a
Linux morgoth.localdomain 3.2.6-3.fc16.x86_64 #1 SMP Mon Feb 13 20:35:42
UTC 2012 x86_64 x86_64 x86_64
On 2011/12/22 17:40, Joe Zeff wrote:
On 12/22/2011 05:23 PM, jdow wrote:
Get a cheap replacement drive and install fresh on it. See if that works.
Until last month when Social Security kicked in, I had no income. Literally. A
"cheap replacement drive" is still a big chunk of my monthly income,
On 12/22/2011 05:23 PM, jdow wrote:
Get a cheap replacement drive and install fresh on it. See if that works.
Until last month when Social Security kicked in, I had no income.
Literally. A "cheap replacement drive" is still a big chunk of my
monthly income, not to be considered lightly, espe
might have something to do with
it. I'm seriously considering uninstalling all 3.X kernels, rebooting and
updating the kernel to see if that helps. And, I'd still like to know how having
/var/log/messages active would have been much of a help because AFAICT, most of
the info I need doesn&#x
do with it. I'm
seriously considering uninstalling all 3.X kernels, rebooting and
updating the kernel to see if that helps. And, I'd still like to know
how having /var/log/messages active would have been much of a help
because AFAICT, most of the info I need doesn't get put there
On 2011/12/22 16:53, Craig White wrote:
On Thu, 2011-12-22 at 13:16 -0800, jdow wrote:
One could observe that Windows tends to get this right. One could observe
your attitude matches with "It was hard to write, it should be hard to use!"
One could observe that this is a sign of acceptance of sl
On Thu, 2011-12-22 at 13:16 -0800, jdow wrote:
> One could observe that Windows tends to get this right. One could observe
> your attitude matches with "It was hard to write, it should be hard to use!"
> One could observe that this is a sign of acceptance of sloppiness. And there
> are more things
On 2011/12/22 14:19, Reindl Harald wrote:
On 22.12.2011 22:16, jdow wrote:
Careful sir, you just stepped into the brown pile the doggie left.
One could observe that Windows tends to get this right. One could observe
your attitude matches with "It was hard to write, it should be hard to use!"
O
On 22.12.2011 23:55, Joe Zeff wrote:
> On 12/22/2011 02:19 PM, Reindl Harald wrote:
>> if you call it arrogance to check what i am doing before, while and
>> especially AFTER a dist-upgrade so i am arrogant - better this than
>> doing anything without verify
>
> No, but it is arrogance to put an
On 12/22/2011 02:19 PM, Reindl Harald wrote:
if you call it arrogance to check what i am doing before, while and
especially AFTER a dist-upgrade so i am arrogant - better this than
doing anything without verify
No, but it is arrogance to put another member of the list (me, as it
happens) for n
On 22.12.2011 22:16, jdow wrote:
> Careful sir, you just stepped into the brown pile the doggie left.
>
> One could observe that Windows tends to get this right. One could observe
> your attitude matches with "It was hard to write, it should be hard to use!"
> One could observe that this is a sig
On 12/22/2011 4:16 PM, jdow wrote:
Your arrogance seems to have tripped you up, sir.
his posts drip with disdain, lording his far superior practices, and
heaping scorn on the lesser mortals he's supposedly here to help...(at
least, I thought that was the purpose of this list)
--
Claude Jone
On 12/22/2011 4:01 PM, Joe Zeff wrote:
On 12/22/2011 11:24 AM, Claude Jones wrote:
On 12/22/2011 1:54 PM, Joe Zeff wrote:
I just saw that the url I gave for the BZ was incomplete:
https://bugzilla.redhat.com/show_bug.cgi?id=769918
thanks, just added a comment to confirm your report
Great!
On 12/22/2011 01:04 PM, Reindl Harald wrote:
however, do not check this after dist-upgrades is a epic-fail
how do you debig all the other problems you wrote about if least
your syslog does not work?
Apples and oranges here, because you're working in a production
environment and I'm only deali
On 2011/12/22 10:58, Reindl Harald wrote:
On 22.12.2011 19:40, Joe Zeff wrote:
On 12/22/2011 07:17 AM, Tim wrote:
"The rule for migration to systemd is to "start-over fresh" with default
start and stop policy from the new package, and not to migrate what the
user had previously configured."
sound still doesn't work, why I can
> only mount USB drives or CDs as root (and I still can't get USB drives world
> writable.) and trying to clean up all
> of the duplicate packages left by a hung install. Yesterday, while looking
> into the USB/CD issue I happened t
On 12/22/2011 11:24 AM, Claude Jones wrote:
On 12/22/2011 1:54 PM, Joe Zeff wrote:
I just saw that the url I gave for the BZ was incomplete:
https://bugzilla.redhat.com/show_bug.cgi?id=769918
thanks, just added a comment to confirm your report
Great! I see that you got hit going from F15 t
USB/CD issue I happened to stumble on the rsyslog issue. Tell
me, Tim, how often do you need to examine /var/log/messages?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines:
On 12/22/2011 10:44 AM, Claude Jones wrote:
I tried, but your link just took me into the login page; I logged in and
then I got an error saying "You must specify a product first" - Tried a
second time, but only got a blank bug reporting page ready to be filled
in - no trace in all of this of your
On 12/22/2011 1:54 PM, Joe Zeff wrote:
I just saw that the url I gave for the BZ was incomplete:
https://bugzilla.redhat.com/show_bug.cgi?id=769918
thanks, just added a comment to confirm your report
--
Claude Jones Brunswick, MD, USA
--
users mailing list
users@lists.fedoraproject.org
To unsu
On 22/12/11 18:56, T.C. Hollingsworth wrote:
On Thu, Dec 22, 2011 at 8:41 AM, Frank Murphy wrote:
Just did it on an F15> F16,
rsyslog came up enabled and running.
Admittedly I did "yum update" on the box.
rsyslog was converted to systemd in F15, so F15->F16 would have just
retained the enabl
On 22.12.2011 19:40, Joe Zeff wrote:
> On 12/22/2011 07:17 AM, Tim wrote:
>> "The rule for migration to systemd is to "start-over fresh" with default
>> start and stop policy from the new package, and not to migrate what the
>> user had previously configured."
>
> In other words, the new rule is
On Thu, Dec 22, 2011 at 8:41 AM, Frank Murphy wrote:
> Just did it on an F15 > F16,
> rsyslog came up enabled and running.
> Admittedly I did "yum update" on the box.
rsyslog was converted to systemd in F15, so F15->F16 would have just
retained the enabled state in systemd.
-T.C.
--
users maili
On 12/22/2011 07:41 AM, Frank Murphy wrote:
Just did it on an F15 > F16,
rsyslog came up enabled and running.
Admittedly I did "yum update" on the box.
I just saw that the url I gave for the BZ was incomplete:
https://bugzilla.redhat.com/show_bug.cgi?id=769918
--
users mailing list
users@list
On 12/22/2011 07:41 AM, Frank Murphy wrote:
Just did it on an F15 > F16,
rsyslog came up enabled and running.
Admittedly I did "yum update" on the box.
It's possible that the upgrade method is significant. I used preupgrade
on both my desktop and laptop. The bug struck the desktop but I've y
On 12/22/2011 07:27 AM, Patrick O'Callaghan wrote:
If this is true, it does seem like a radical change. What possible
argument could there be for not logging by default?
I recently saw that the proper way to shut down Linux from the command
line is poweroff. The old command halt now halts the
On 12/22/2011 1:20 PM, Joe Zeff wrote:
On 12/22/2011 01:03 AM, T.C. Hollingsworth wrote:
The fact that it's not being enabled in practice is definitely a bug,
and someone experiencing this should file it.
Done: https://bugzilla.redhat.com/post_bug.cgi
I'd appreciate anybody else on the list f
On 12/22/2011 07:17 AM, Tim wrote:
"The rule for migration to systemd is to "start-over fresh" with default
start and stop policy from the new package, and not to migrate what the
user had previously configured."
In other words, the new rule is to assume that whoever set the system up
and runs
On 12/22/2011 07:17 AM, Tim wrote:
Tim sets the super pedant mode... Do some more research. What I did
*is* accepted correct modern usage of "begs the question."
It's still wrong, just as "Me and Jim went to the mall." is, even though
most people under about 25 or so would swear it's correc
On 12/22/2011 01:03 AM, T.C. Hollingsworth wrote:
The fact that it's not being enabled in practice is definitely a bug,
and someone experiencing this should file it.
Done: https://bugzilla.redhat.com/post_bug.cgi
I'd appreciate anybody else on the list finding this adding comments to
the bug
On 22/12/11 15:27, Patrick O'Callaghan wrote:
So, whatever you had set up beforehand is ignored, and the new default
is implemented. Not logging, by default, doesn't seem a good idea.
If this is true, it does seem like a radical change. What possible
argument could there be for not logging b
On Fri, 2011-12-23 at 01:47 +1030, Tim wrote:
> Tim:
> >> Begs the question: Has this no-logging become a new default, or just a
> >> fault?
>
> Rahul Sundaram:
> > https://fedoraproject.org/wiki/Common_F16_bugs#Upgrade_from_previous_releases_resets_the_enablement_status_of_services
>
>
> Well
Tim:
>> Begs the question: Has this no-logging become a new default, or just a
>> fault?
Rahul Sundaram:
> https://fedoraproject.org/wiki/Common_F16_bugs#Upgrade_from_previous_releases_resets_the_enablement_status_of_services
Well, that seems to suggest that the new default is not to log.
"Th
Tim:
>> Begs the question: Has this no-logging become a new default, or just
>> a fault?
Joe Zeff:
>
> No, it doesn't, it asks the question. Begging the question is
> something entirely different which would better be called assuming
> your conclusion.
Tim sets the super pedant mode... Do som
On 12/22/2011 02:27 AM, Joe Zeff wrote:
On 12/21/2011 11:10 PM, Ralf Corsepius wrote:
I would call it a functional regression having been introduce during by
the sysvinit/upstart->systemd transition.
If it has not been BZ'd before, it should be BZ'ed.
I wouldn't mind being the reporter, but I
On 22.12.2011 10:51, Ralf Corsepius wrote:
> On 12/22/2011 10:06 AM, Reindl Harald wrote:
>>
>>
>> On 22.12.2011 07:27, Joe Zeff wrote:
>>> On 12/21/2011 11:10 PM, Ralf Corsepius wrote:
I would call it a functional regression having been introduce during by
the sysvinit/upstart->systemd
On Thu, 22 Dec 2011 17:30:50 +1030
Tim wrote:
> Begs the question: Has this no-logging become a new default, or just a
> fault?
Maybe doing an upgrade doesn't transfer the on/off setting
from the old chkconfig info to the new systemd info?
Maybe syslog is merely the most noticable of the service
On 12/22/2011 10:06 AM, Reindl Harald wrote:
On 22.12.2011 07:27, Joe Zeff wrote:
On 12/21/2011 11:10 PM, Ralf Corsepius wrote:
I would call it a functional regression having been introduce during by
the sysvinit/upstart->systemd transition.
If it has not been BZ'd before, it should be BZ'ed
On 22.12.2011 07:27, Joe Zeff wrote:
> On 12/21/2011 11:10 PM, Ralf Corsepius wrote:
>> I would call it a functional regression having been introduce during by
>> the sysvinit/upstart->systemd transition.
>>
>> If it has not been BZ'd before, it should be BZ'ed.
>
> I wouldn't mind being the rep
On Thu, Dec 22, 2011 at 1:32 AM, Rahul Sundaram wrote:
> On 12/22/2011 12:30 PM, Tim wrote:
>> On Wed, 2011-12-21 at 20:04 +, Frank Murphy wrote:
>>>
>>> http://lists.fedoraproject.org/pipermail/users/2011-December/410018.html
>>
>> Begs the question: Has this no-logging become a new default,
On 12/22/2011 12:30 PM, Tim wrote:
> On Wed, 2011-12-21 at 20:04 +, Frank Murphy wrote:
>>
>> http://lists.fedoraproject.org/pipermail/users/2011-December/410018.html
>
> Begs the question: Has this no-logging become a new default, or just a
> fault?
https://fedoraproject.org/wiki/Common_F16
On 12/22/2011 08:27 AM, Joe Zeff wrote:
On 12/21/2011 11:10 PM, Ralf Corsepius wrote:
I would call it a functional regression having been introduce during by
the sysvinit/upstart->systemd transition.
If it has not been BZ'd before, it should be BZ'ed.
I wouldn't mind being the reporter, but I
On 12/21/2011 11:10 PM, Ralf Corsepius wrote:
I would call it a functional regression having been introduce during by
the sysvinit/upstart->systemd transition.
If it has not been BZ'd before, it should be BZ'ed.
I wouldn't mind being the reporter, but I'd like to know if anybody else
sees thi
On Thu, 2011-12-22 at 08:10 +0100, Ralf Corsepius wrote:
> On 12/22/2011 08:00 AM, Tim wrote:
> > On Wed, 2011-12-21 at 20:04 +, Frank Murphy wrote:
> >>
> >> http://lists.fedoraproject.org/pipermail/users/2011-December/410018.html
> >
> > Begs the question: Has this no-logging become a new de
On 12/21/2011 11:00 PM, Tim wrote:
Begs the question: Has this no-logging become a new default, or just a
fault?
No, it doesn't, it asks the question. Begging the question is something
entirely different which would better be called assuming your
conclusion. The term comes from a form of
On 12/22/2011 08:00 AM, Tim wrote:
On Wed, 2011-12-21 at 20:04 +, Frank Murphy wrote:
http://lists.fedoraproject.org/pipermail/users/2011-December/410018.html
Begs the question: Has this no-logging become a new default, or just a
fault?
I would call it a functional regression having be
On Wed, 2011-12-21 at 20:04 +, Frank Murphy wrote:
>
> http://lists.fedoraproject.org/pipermail/users/2011-December/410018.html
Begs the question: Has this no-logging become a new default, or just a
fault?
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replie
On 12/21/2011 01:13 PM, Alan J. Gagne wrote:
Try here !
http://fedoraproject.org/wiki/Systemd
Thanx, Alan, I've bookmarked it JIC.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guideline
Try here !
http://fedoraproject.org/wiki/Systemd
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: h
On 12/21/2011 12:04 PM, Frank Murphy wrote:
On 21/12/11 19:59, Joe Zeff wrote:
http://lists.fedoraproject.org/pipermail/users/2011-December/410018.html
Excellent. Thank you. The odd thing here is that the link mentioned in
that post already existed. And, I'd still appreciate a cheat she
On 21/12/11 19:59, Joe Zeff wrote:
http://lists.fedoraproject.org/pipermail/users/2011-December/410018.html
--
Regards,
Frank Murphy
UTF_8 Encoded
Friend of fedoraproject.org
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedor
I just tried to check something in /var/log/messages and noticed
something: the last entry was on Dec 6 when I rebooted to start the
upgrade from F14 to F16. Since then, nothing. I presume that something
was turned off during the upgrade but I don't know what and I don't know
the
Am 31.08.2011 15:38, schrieb antonio.montagn...@alice.it:
>>> How is it possible??
>>
>
>> Are you running F15?
>>
>> Try systemctl restart syslog.target . There was a bug
> in F15 that
>> caused this. I can't remember the fix, though. You might try
>
>> systemctl enable syslog.service .
>
On Wed, 2011-08-31 at 08:55 -0400, Garry T. Williams wrote:
> On Wednesday, August 31, 2011 14:11:15 antonio.montagn...@alice.it wrote:
> > I checked all files in var/log and in particular I found these files are 0
> > bytes.
> >
> > How is it possible??
>
> Are you running F15?
>
> Try systemc
On Wed, 31 Aug 2011 15:38:01 +0200 (CEST)
"antonio.montagn...@alice.it" wrote:
> [root@Acer antonio]
> # systemctl enable syslog.service
> Couldn't find syslog.service.
>
>
> what is
> wrong??
The system is called rsyslog.
Run
systemctl -a -t service | less
to see all the services availab
>Messaggio originale
>Da: m...@avtechpulse.com
>Data: 31-ago-2011
15.59
>A:
>Ogg: Re: R: Re: Var/log/messages
file are empty
>
>> [root@Acer antonio]
>> # systemctl enable syslog.service
>>
Couldn't find syslog.service.
>
>
&g
> [root@Acer antonio]
> # systemctl enable syslog.service
> Couldn't find syslog.service.
systemctl enable rsyslog.service
(add the "r")
- Mike
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/us
>Messaggio originale
>Da: gtwilli...@gmail.com
>Data: 31-ago-2011
14.55
>A: "antonio.montagn...@alice.it",
"Community support for Fedora users"
>Ogg: Re:
Var/log/messages file are empty
>
>On Wednesday, August 31, 2011 14:11:15
antonio.mo
On Wednesday, August 31, 2011 14:11:15 antonio.montagn...@alice.it wrote:
> I checked all files in var/log and in particular I found these files are 0
> bytes.
>
> How is it possible??
Are you running F15?
Try systemctl restart syslog.target . There was a bug in F15 that
caused this. I can't
I checked all files in var/log and in particular I found these files are 0
bytes.
How is it possible??
Tnx
Antonio
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedora
#kern.* /dev/console <
chnged
kern.* /var/log/messages
Seems to solve logging problem
Jarmo
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listi
I'm confused, /var/log/messages is empty. FC15
multi-user.target.wants]# systemctl status rsyslog.service
rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service)
Active: active (running) since Wed, 13 Jul 2011 17:20:03 +0300;
24mi
that
> they'll only notice when they need to look at a log and it's not there.
> In my case I lost three weeks worth of /var/log/messages.
>
> Note that a simple yum update does not fix this.
That's true for the pioneers. :-)
At least the QA folks want to make sure it
1 - 100 of 140 matches
Mail list logo
