"Patrick Dupre" writes:
> 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 th
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 a chance to
when your compute
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 unsubscribe or change subscription optio
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 installed?
>
> Here's my logs:
>
> zoo
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 /var/log/messages
-rw
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 descrip
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
On 2011/12/22 17:16, Joe Zeff wrote:
On 12/22/2011 04:29 PM, jdow wrote:
(Joe MIGHT have been wise to move to 15 from 14 then move to 16 from 15 as
the upgrade path would have smaller changes. 14 to 15 might have properly
caught his syslogd problem. I'm not looking forward to the day the RHEL
p
On 12/22/2011 04:29 PM, jdow wrote:
(Joe MIGHT have been wise to move to 15 from 14 then move to 16 from 15 as
the upgrade path would have smaller changes. 14 to 15 might have properly
caught his syslogd problem. I'm not looking forward to the day the RHEL
path
adopts systemd. It sounds like mor
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."
On 22.12.2011 21:57, Joe Zeff wrote:
> On 12/22/2011 10:58 AM, 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 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
On 12/22/2011 10:58 AM, 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 previous
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
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
jarmo kirjoitti keskiviikko, 13. heinäkuuta 2011 17:51:03:
> does write nothing into messages.
> Where to look solution?
Just found something...
In /etc/rsyslog.conf:
RULES
On Saturday, June 11, 2011 22:06:06 Patrick O'Callaghan wrote:
> All the same, I can't help wondering why this wasn't considered a
> blocker, given that it was known about before F15 was released.
QA called it a "nice to have". I think they thought it was going to
be fixed in a zero-day update:
On Sun, 2011-06-12 at 08:59 +0800, Ed Greshko wrote:
> On 06/12/2011 08:54 AM, Patrick O'Callaghan wrote:
> > According to https://bugzilla.redhat.com/show_bug.cgi?id=699198 it
> > depends when you did the upgrade. Early birds got screwed on this one.
>
> I knew there would be a reward for procras
On 06/12/2011 08:54 AM, Patrick O'Callaghan wrote:
> According to https://bugzilla.redhat.com/show_bug.cgi?id=699198 it
> depends when you did the upgrade. Early birds got screwed on this one.
I knew there would be a reward for procrastination. :-)
--
users mailing list
users@lists.fedorapro
On Sun, 2011-06-12 at 07:57 +0800, Ed Greshko wrote:
> On 06/12/2011 07:17 AM, Patrick O'Callaghan wrote:
> > I just had occasion to look at /var/log/messages for the first time in a
> > while and there's nothing in it. I think this dates from my updating F14
> > to F15.
> >
> > /etc/syslog.conf lo
On Sat, 2011-06-11 at 20:20 -0400, Garry T. Williams wrote:
> On Saturday, June 11, 2011 19:17:09 Patrick O'Callaghan wrote:
> > I just had occasion to look at /var/log/messages for the first time
> > in a while and there's nothing in it. I think this dates from my
> > updating F14 to F15.
>
> Thi
On Saturday, June 11, 2011 19:17:09 Patrick O'Callaghan wrote:
> I just had occasion to look at /var/log/messages for the first time
> in a while and there's nothing in it. I think this dates from my
> updating F14 to F15.
This is a bug[*] in the F15 update. The fix is:
sudo systemctl enable
On 06/12/2011 07:17 AM, Patrick O'Callaghan wrote:
> I just had occasion to look at /var/log/messages for the first time in a
> while and there's nothing in it. I think this dates from my updating F14
> to F15.
>
> /etc/syslog.conf looks normal. This is the relevant stanza:
>
> # Log anythi
On Saturday, June 11, 2011 07:05:20 Garry T. Williams wrote:
> On Saturday, June 11, 2011 06:08:10 Joshua C. wrote:
> > After I upgraded ot f15 I see that all messages are sent to dmesg
> > but after several days the /var/log/messages is still empty. So my
> > logs get deleted after every restart.
On Sat, Jun 11, 2011 at 6:08 AM, Joshua C. wrote:
>
> After I upgraded ot f15 I see that all messages are sent to dmesg but
> after several days the /var/log/messages is still empty. So my logs
> get deleted after every restart. How to fix this?
Check "/etc/rsyslog.conf" for a "/var/log/messages"
On Saturday, June 11, 2011 06:08:10 Joshua C. wrote:
> After I upgraded ot f15 I see that all messages are sent to dmesg
> but after several days the /var/log/messages is still empty. So my
> logs get deleted after every restart. How to fix this?
sudo systemctl enable rsyslog.service
sudo
On Wed, 2011-06-01 at 14:47 +0100, Mark Knoop wrote:
> At 07:40 on 01 Jun 2011, Patrick O'Callaghan wrote:
> > On Wed, 2011-06-01 at 05:22 -0400, Tom Horsley wrote:
> > > On Wed, 01 Jun 2011 11:51:18 +0930
> > > Tim wrote:
> > >
> > > > You mean like the old boot.log file, that was going to be
> >
At 07:40 on 01 Jun 2011, Patrick O'Callaghan wrote:
> On Wed, 2011-06-01 at 05:22 -0400, Tom Horsley wrote:
> > On Wed, 01 Jun 2011 11:51:18 +0930
> > Tim wrote:
> >
> > > You mean like the old boot.log file, that was going to be
> > > improved, and was disabled in the meantime, then never was
> >
On Wed, 2011-06-01 at 05:22 -0400, Tom Horsley wrote:
> On Wed, 01 Jun 2011 11:51:18 +0930
> Tim wrote:
>
> > You mean like the old boot.log file, that was going to be improved, and
> > was disabled in the meantime, then never was improved?
>
> Look again :-). All the changes to boot graphically
On Wed, 01 Jun 2011 11:51:18 +0930
Tim wrote:
> You mean like the old boot.log file, that was going to be improved, and
> was disabled in the meantime, then never was improved?
Look again :-). All the changes to boot graphically brought
with them one good feature - there is a boot.log file now.
-
On Wed, 2011-06-01 at 11:51 +0930, Tim wrote:
> On Tue, 2011-05-31 at 12:12 -0430, Patrick O'Callaghan wrote:
> > I think it would be simpler if each new boot simply started a
> > new log file.
>
> You mean like the old boot.log file, that was going to be improved, and
> was disabled in the meanti
On Tue, 2011-05-31 at 12:12 -0430, Patrick O'Callaghan wrote:
> I think it would be simpler if each new boot simply started a
> new log file.
You mean like the old boot.log file, that was going to be improved, and
was disabled in the meantime, then never was improved?
--
[tim@localhost ~]$ uname
On 05/31/2011 07:25 AM, R. G. Newbury wrote:
> It is far easier to add: echo "Completed boot at `date`"
>
> to the bottom of /etc/rc.d/rc.local
>
> Then it does not matter whether the system is using the old method or
> systemd and whether it is writing to 'messages' or boot.log.
The whole point
On Tue, 2011-05-31 at 12:28 -0400, Tom Horsley wrote:
> On Tue, 31 May 2011 10:17:56 -0600
> Phil Meyer wrote:
>
> > So in summary, if you see a syslog startup, followed within a few lines
> > by the word ' Linux ', and what comes after that appear to be BIOS info,
> > and that all these message
On Tue, 31 May 2011 10:17:56 -0600
Phil Meyer wrote:
> So in summary, if you see a syslog startup, followed within a few lines
> by the word ' Linux ', and what comes after that appear to be BIOS info,
> and that all these messages happen in the same second or two, you have
> found the top of t
On 05/31/2011 08:25 AM, R. G. Newbury wrote:
>> On Mon, 2011-05-30 at 18:36 -0400, Tom Horsley wrote:
Just for curiosity, why has no one ever arranged to
log something like "Hey! I'm booting the system again!"
as the very first line in that goes to /var/log/messages
when
> On Mon, 2011-05-30 at 18:36 -0400, Tom Horsley wrote:
>> > Just for curiosity, why has no one ever arranged to
>> > log something like "Hey! I'm booting the system again!"
>> > as the very first line in that goes to /var/log/messages
>> > when the system is booting?
> I used to do something l
On 05/30/2011 09:07 PM, Joe Zeff wrote:
> On 05/30/2011 05:42 PM, Timothy Murphy wrote:
>> Tom Horsley wrote:
>>
>>> If would be real convenient to have a known string to
>>> search for that always precedes the rest of the messages
>>> in a new boot.
>>
>> I agree.
>> Even a couple of blank lines w
On Mon, 2011-05-30 at 19:07 -0700, Joe Zeff wrote:
> On 05/30/2011 05:42 PM, Timothy Murphy wrote:
> > Tom Horsley wrote:
> >
> >> If would be real convenient to have a known string to
> >> search for that always precedes the rest of the messages
> >> in a new boot.
> >
> > I agree.
> > Even a coup
On Mon, 2011-05-30 at 18:36 -0400, Tom Horsley wrote:
> Just for curiosity, why has no one ever arranged to
> log something like "Hey! I'm booting the system again!"
> as the very first line in that goes to /var/log/messages
> when the system is booting?
I used to do something like that back when
On 05/30/2011 07:07 PM, Joe Zeff wrote:
> On 05/30/2011 05:42 PM, Timothy Murphy wrote:
>> Tom Horsley wrote:
>>
>>> If would be real convenient to have a known string to
>>> search for that always precedes the rest of the messages
>>> in a new boot.
>>
>> I agree.
>> Even a couple of blank lines w
On 05/30/2011 05:42 PM, Timothy Murphy wrote:
> Tom Horsley wrote:
>
>> If would be real convenient to have a known string to
>> search for that always precedes the rest of the messages
>> in a new boot.
>
> I agree.
> Even a couple of blank lines would help.
>
>
Indeed. Am I the only one on the
Tom Horsley wrote:
> If would be real convenient to have a known string to
> search for that always precedes the rest of the messages
> in a new boot.
I agree.
Even a couple of blank lines would help.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-m
On Mon, 30 May 2011 16:05:07 -0700
Peter Gordon wrote:
> imklog 5.7.9, log source = /proc/kmsg started.
Yea, the same thing starts mine, but I just thought
it would be nice to have something more obvious
(and perhaps less likely to change someday :-).
--
users mailing list
users@lists.fedoraproj
On 05/30/2011 03:36 PM, Tom Horsley wrote:
> If would be real convenient to have a known string to
> search for that always precedes the rest of the messages
> in a new boot.
You could try grep'ing for the Linux version string, always one of the
first several lines printed during kernel startup. T
95 matches
Mail list logo
