Hi there,
I'm using busybox-syslogd. I'm trying to make it log to remote system
and to memory buffer. According to manual I should use -R 192.168.1.1
for remote logging and -C128 option for memory buffer. Unfortunately,
when used together logs are only sent to remote server. On Bo
Hello,
I found your thread and I wanted to add something I found on my system.
If I add additional drives (either network or internal) into the fstab
file the system hangs for the 4+ minutes stated.
If I do not add the drives the system acts normally during shutdown/restart.
I also noted that
On 2014-08-29, Michael Biebl wrote:
> But yeah, isn't it great if you can everything on systemd.
>
Systemd is wonderful.
I made a "little" mistake.
I'll shoot myself at dawn.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Am 29.08.2014 10:24, schrieb Curt:
> On 2014-08-29, Devrin Talen wrote:
>
>> Since it's related to the /etc/rc0.d scripts, maybe start with a bug
>> against the sysv-rc package?
>>
>> $ dpkg --search /etc/rc0.d/
>> sysv-rc: /etc/rc0.d
>>
>> You can check if your bug is already there (a qu
On 2014-08-29, Curt wrote:
>
> Looks rather like this bug (maybe samba, maybe systemd in its troubled
> relationship to samba or sumthin').
>
Forgot the bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739887
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subje
On 2014-08-29, Devrin Talen wrote:
> Since it's related to the /etc/rc0.d scripts, maybe start with a bug
> against the sysv-rc package?
>
> $ dpkg --search /etc/rc0.d/
> sysv-rc: /etc/rc0.d
>
> You can check if your bug is already there (a quick search didn't show
> anything):
>
Looks r
David Christensen writes:
> If I manually unmount Samba shared folders imported by this machine
> prior to shutdown, shutdown proceeds without delay. So, the problem
> appears to be related to the order in which things happen at shutdown
> (?).
>
> Any ideas on how to troubleshoot and properly f
: Sending processes the TERM signal
[info] Using makefile-style concurrent boot in runlevel 6.
...
[ OK ] Asking all remaining processes to terminate...done.
[ OK [ All processes ended within 1 seconds...done.
[ OK ] Stopping enhanced syslogd: rsyslog.
After 4+ minutes, shutdown
processes the TERM signal
[info] Using makefile-style concurrent boot in runlevel 6.
...
[ OK ] Asking all remaining processes to terminate...done.
[ OK [ All processes ended within 1 seconds...done.
[ OK ] Stopping enhanced syslogd: rsyslog.
After 4+ minutes, shutdown resumes and the
TERM signal
[info] Using makefile-style concurrent boot in runlevel 6.
...
[ OK ] Asking all remaining processes to terminate...done.
[ OK [ All processes ended within 1 seconds...done.
[ OK ] Stopping enhanced syslogd: rsyslog.
After 4+ minutes, shutdown resumes and the machine
On Mon, 18 Jun 2012 12:34:49 +0200 "Alberto Fuentes
alberto.fuen...@qindel.com" suggested this:
>If you dont have any raid and it changed names for you too maybe is
>not just my raid case :S
I don't have any raid aL.
My external hard drive mounts with UUID and also says that /media/usb0
is mou
On 06/18/2012 11:57 AM, Charlie wrote:
[...]
does it shift between remounts or does it shift names live?
It used to shift live.
[...]
Maybe with raid the problem is different?
Well, its a hardware raid and its presented to the system as a single
disk. I have to pass a few parameters to
On Mon, 18 Jun 2012 08:44:42 +0200 "Alberto Fuentes
alberto.fuen...@qindel.com" suggested this:
>On 06/16/2012 02:31 PM, Charlie wrote:
>> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
>>
>> I am now mounting it as /dev/sdb1. That's what it has always been,
>> and then it sta
On 06/16/2012 02:31 PM, Charlie wrote:
It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
I am now mounting it as /dev/sdb1. That's what it has always been, and
then it started to drop out while I was looking through the files and
wouldn't mount and came up as /dev/sdd1 etc..
It
Good time of the day, Charlie.
You worte:
> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
Oh, I got it now - You did not mention that.
> I am now mounting it as /dev/sdb1. That's what it has always been, and
> then it started to drop out while I was looking through the file
On Sun, 17 Jun 2012 08:43:49 +1000, Charlie wrote:
> On Sat, 16 Jun 2012 17:13:26 + (UTC) "Camaleón noela...@gmail.com"
> suggested this:
>>Being USB volumes in external enclosures it can be that they were badly
>>umounted and thus the message. I would run "fsck" over the umounted
>>volumes
On Sun, 17 Jun 2012 10:45:26 +0100 "keith km3...@gmail.com" suggested
this:
>On Sat, 2012-06-16 at 22:31 +1000, Charlie wrote:
>
>> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
>>
>> I am now mounting it as /dev/sdb1. That's what it has always been,
>> and then it started t
On Sat, 2012-06-16 at 22:31 +1000, Charlie wrote:
> It changes the device from /dev/sdb1 to /dev/sdd1 and back again.
>
> I am now mounting it as /dev/sdb1. That's what it has always been, and
> then it started to drop out while I was looking through the files and
> wouldn't mount and came up as
systems:
>>
>> Message from syslogd@nomad at Jun 16 08:04:30 ...
>> kernel:[ 3187.986721] journal commit I/O error
>
>Being USB volumes in external enclosures it can be that they were
>badly umounted and thus the message. I would run "fsck" over the
>umounte
On Sat, 16 Jun 2012 08:14:03 +1000, Charlie wrote:
> This happens with both powered and powered only through a USB
> connection, external hard drives. Both with ext3 file systems:
>
> Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721]
> journal commit I/O e
On Sat, 16 Jun 2012 11:30:34 +0700 "Sthu Deus sthu.d...@gmail.com"
suggested this:
>> mount /mnt/lpics
>> mount: special device /dev/sdd1 does not exist
>
>Why don't You mount /dev/sdb1 but /dev/sdd1 ?
>
>Also, You can mount by UUID.
>
>What I would do in Your situation is:
>
>. connect HDD d
Good time of the day, Charlie.
You worte:
> Tried different cabling:
>
> blkid says,
>
> /dev/sdb1: UUID="4bb48afe-02d7-487f-a51f-ff378edbc98d" TYPE="ext3"
>
> Then in a terminal:
>
> mount /mnt/lpics
> mount: special device /dev/sdd1 does not exist
Why don't You mount /dev/sdb1 but /dev/s
On Fri, 15 Jun 2012 23:48:12 +0700 "Sthu Deus sthu.d...@gmail.com"
suggested this:
>Good time of the day, Charlie.
>
>
>You worte:
>
>> This happens with both powered and powered only through a
>> USB connection, external hard drives. Both with ext3 file
Good time of the day, Charlie.
You worte:
> This happens with both powered and powered only through a
> USB connection, external hard drives. Both with ext3 file systems:
>
> Message from syslogd@nomad at Jun 16 08:04:30 ...
> kernel:[ 3187.986721] journal commit I/O error
&
ile systems:
>>
>> Message from syslogd@nomad at Jun 16 08:04:30 ...
>> kernel:[ 3187.986721] journal commit I/O error
>
>This seems regular error in disks to me. If you have tried the disks
>in stable and it does not show in syslog, maybe it was just added to
>show, but it d
On 06/16/2012 12:14 AM, Charlie wrote:
This happens with both powered and powered only through a
USB connection, external hard drives. Both with ext3 file systems:
Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721]
journal commit I/O error
This seems regular error in
This happens with both powered and powered only through a
USB connection, external hard drives. Both with ext3 file systems:
Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721]
journal commit I/O error
Seems to be more funny things happening with this testing system than
On Thu, Apr 22, 2010 at 07:24:38PM -0400, Nick Lidakis wrote:
> This popped up in one of my xterms after my Thinkpad came out of hibernation
> today. The machine has beeped a few times as this message was repeated.
> Does not sound good. Call Trace? That's, like, bad? Right?
>
>
> Message from sy
On Thu, 22 Apr 2010 19:24:38 -0400, Nick Lidakis wrote:
> This popped up in one of my xterms after my Thinkpad came out of
> hibernation today. The machine has beeped a few times as this message
> was repeated. Does not sound good. Call Trace? That's, like, bad? Right?
>
>
> Message from sysl...
This popped up in one of my xterms after my Thinkpad came out of hibernation
today. The machine has beeped a few times as this message was repeated.
Does not sound good. Call Trace? That's, like, bad? Right?
Message from sysl...@thinkpad at Apr 22 18:52:20 ...
kernel:[42926.069917] Oops: [#
Tom Schmitt wrote:
> My question: Is there a goog reason for this
Yes, it allows automatically rotating all log files configured in
/etc/syslog.conf, even if you modify the file and add new ones, without
needing to update a separate logrotate configuration file.
--
see shy jo
signature.asc
Des
On Sun, 2007-04-01 at 22:00 +0200, Tom Schmitt wrote:
> Some logfiles are rotated with logrotated, which is
> quite confortable. But the syslogd-logfiles have their
> own script to rotate them.
>
> My question: Is there a goog reason for this or could I
> delete the syslog-scr
Hi,
I setup a server with Debian Etch and had a look at the
handling of th logfiles.
Some logfiles are rotated with logrotated, which is
quite confortable. But the syslogd-logfiles have their
own script to rotate them.
My question: Is there a goog reason for this or could I
delete the syslog
On Sat, Nov 12, 2005 at 12:34:28PM +0100, Roy wrote:
> In /var/log/messages the following lines are apprearing:
Good... they're supposed to be. Means your machine is alive and syslog is
running.
> What is the correct command to use in debian?
Why stop them?
--
Marc Wilson | I must follo
f them, but i'm getting an
> error message: syslogd: no process killed. -Bash: /usr/sbin/syslogd: no such
> file or directory.
>
> # killall syslogd; /usr/sbin/syslogd -m -o
If you want t turn off the MARK lines edit /etc/init.d/sysklogd
and set the mark interval to zero:
SY
In /var/log/messages the following lines
are apprearing:
Date Time machine name -- MARK
--
Date Time machine name -- MARK
--
Date Time machine name -- MARK
--
I'm using the following command, below to get
rid of them, but i'm getting an error message: syslogd:
On Thu, Dec 02, 2004 at 05:54:19PM -0800, jack kinnon wrote:
> I'm still stuck with this problem.
>
> syslogd : cannot create /dev/log : address family not supported by protocol
>
> The whole system is working only in basic command-line mode. Someone
> suggested
> HI,
>
> I'm still stuck with this problem.
>
> syslogd : cannot create /dev/log : address family not supported by
> protocol
I didn't notice that you have asked before, so I don't know what has already
been suggested... but if the _address family_ is unsuppor
HI,
I'm still stuck with this problem.
syslogd : cannot create /dev/log : address family not supported by protocol
The whole system is working only in basic command-line mode. Someone suggested downloading the 'Debian Installer' but that would eat into my monthly subscripti
Im running the 2.6.0-1-k7 kernel with debian unstable and
today I find messages like these have been written to the eterm
window I had left open:
Message from [EMAIL PROTECTED] at Sun Mar 7 01:27:17 2004 ...
dhunt kernel: MCE: The hardware reports a non fatal, correctable
incident occurr
ed on
Adam Byrtek wrote:
- unmaintained
I'll try to maintain it better then the previous maintainer...
I'm a user of debian unstable on the desktop.
I'm glad to see this, I was slightly confused that one day i saw this
package removed, checked bug reports and didn't find anything reasonable
about the 'w
syslogd(three): some logger thread(s) are stuck (including the console);
syslogd is shutting down.
Anyone has much info about this error? Why is this happening??
--
thanks,
louie miranda
chikka asia, inc.
noc +63-2(7535000-511)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
I found the problem!
- Original Message -
From:
dizma
To: [EMAIL PROTECTED]
Sent: Tuesday, September 24, 2002 4:44
PM
Subject: syslogd $ logrotate
Hi there,
I'm running Woody
My syslog daemon doesn't log any thing after
logrotate was run
Hi there,
I'm running Woody
My syslog daemon doesn't log any thing after
logrotate was run?
NN
---Risk
Engineering Ltd. Nikodim
Nikodimov34 Totleben
Bulv.
System AdministratorSofia 1604,
Bulgaria e-ma
I see syslogd-listfiles and savelog at heart of /etc/cron.daily/sysklogd.
Are these methods unique to Debian? I use RH6.1 and Mandrake 8.1 and they do
not have syslogd-listfiles or savelog commands.
On my RH6.1 systems (slated for migration to Debian) the logrotate facility
is used to in
Raffaele Sandrini, 2001-Nov-09 19:13 +0100:
> Hi all,
>
> what do i have to enter to the sylog.conf to split all the iptables messages
> done by the LOG (-j LOG) target into another file than messages?
>
> cheers,
> Raffaele
> --
syslog doesn't allow this functionality. You need to replace it
Hi all,
what do i have to enter to the sylog.conf to split all the iptables messages
done by the LOG (-j LOG) target into another file than messages?
cheers,
Raffaele
--
Raffaele Sandrini <[EMAIL PROTECTED]>
For encrypted Mail get my Public Key from "search.keyserver.net"
ID: 0xEC4950E9
Anybody seen this repeated on their console:
syslogd: unknown priority name ""
I cannot find it in any file under /var/log.
It looks like some application is not behaving properly when
communicating with syslogd.
How can I find the offending little bugger?
What do
#x27;t even have the slightest clue
> why) when booting the message:
>
> "Starting system log daemon: syslogd"
>
> sits on the screen for about 5 minutes (literally!) with no signs of the
> computer even doing anything. The HD/Cd-rom lights are not flashing. It's
&
log daemon: syslogd"
sits on the screen for about 5 minutes (literally!) with no signs of the
computer even doing anything. The HD/Cd-rom lights are not flashing. It's
just sitting there. Eventually it does start up and everything works fine.
Any ideas of where to start on this one
Thank you.
Moritz Schulte wrote:
>
> "Michael D. Schleif" <[EMAIL PROTECTED]> writes:
>
> > Where and how is syslogd started at bootup?
>
> /etc/init.d/sysklogd is the init script. This gets called via the
> links in /etc/rc?.d/ (or via /etc/
"Michael D. Schleif" <[EMAIL PROTECTED]> writes:
> Where and how is syslogd started at bootup?
/etc/init.d/sysklogd is the init script. This gets called via the
links in /etc/rc?.d/ (or via /etc/runlevel.conf, if you're using
file-rc).
moritz
--
Moritz Schulte
Where and how is syslogd started at bootup?
--
Best Regards,
mds
mds resource
888.250.3987
"Dare to fix things before they break . . . "
"Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . . "
On Sun, Jan 21, 2001 at 02:18:38AM -0500, Arcady Genkin wrote:
> Hmm. And from where did you think I pulled out that one? :^)
>
> ,[ syslog.conf(5) ]
> |The facility is one of the following keywords: auth, auth
> |priv, cron, daemon, kern, lpr, mail, mark, news, security
>
Arcady Genkin wrote:
> mike polniak <[EMAIL PROTECTED]> writes:
>
> > > As I wrote in my previous message, ever since I added "cron.!info;" to
> > > the line that pipes to /dev/xconsole, I am not seeing the exim cron
> > > notifications any more.
> >
> > Did you mean : cron.!=info; ?
> >
mike polniak <[EMAIL PROTECTED]> writes:
> > As I wrote in my previous message, ever since I added "cron.!info;" to
> > the line that pipes to /dev/xconsole, I am not seeing the exim cron
> > notifications any more.
>
> Did you mean : cron.!=info; ?
>^^
Thank yo
>
> As I wrote in my previous message, ever since I added "cron.!info;" to
> the line that pipes to /dev/xconsole, I am not seeing the exim cron
> notifications any more.
Did you mean : cron.!=info; ?
^^
--
~~~
"Noah L. Meyerhans" <[EMAIL PROTECTED]> writes:
> There's no such syslog facility "cron". Cron logs to the 'daemon'
> facility. The only way to tweak what cron messages you see is to adjust
> what daemon priorities get logged. Read the syslog and syslog.conf man
> pages.
Hmm. And from where d
On Sat, Jan 20, 2001 at 06:36:44PM -0500, Arcady Genkin wrote:
> "Noah L. Meyerhans" <[EMAIL PROTECTED]> writes:
>
> > Well, if you look at the line that's logged, you'll see that it's not
> > coming from Exim at all, but from cron. So changing the way syslog
> > handles the mail facility won't h
"Noah L. Meyerhans" <[EMAIL PROTECTED]> writes:
> Well, if you look at the line that's logged, you'll see that it's not
> coming from Exim at all, but from cron. So changing the way syslog
> handles the mail facility won't help.
Yes, that's why I tried adding "cron.!*" to the rule. But it see
mike polniak <[EMAIL PROTECTED]> writes:
> > How would I get rid of the message about exim cron job being printed
> > at /dev/xconsole? This job runs every 20 minutes and I would like not
> > to see reports of it unless there was an error.
> >
> Edit /etc/cron.d/exim file.
This would let
Arcady Genkin wrote:
> How would I get rid of the message about exim cron job being printed
> at /dev/xconsole? This job runs every 20 minutes and I would like not
> to see reports of it unless there was an error.
>
> , [ /dev/xconsole ]
> | Jan 20 14:38:01 tea /USR/SBIN/CRON[5850]: (mail) C
Well, if you look at the line that's logged, you'll see that it's not
coming from Exim at all, but from cron. So changing the way syslog
handles the mail facility won't help. Also, exim is configured by
default (on debian) to handle its own logging and not go through syslog.
The cron logs come f
How would I get rid of the message about exim cron job being printed
at /dev/xconsole? This job runs every 20 minutes and I would like not
to see reports of it unless there was an error.
,[ /dev/xconsole ]
| Jan 20 14:38:01 tea /USR/SBIN/CRON[5850]: (mail) CMD ( if [ -x \
| /usr/sbin/exi
hi
i've got a very strange prob when my system changes into runlevle 2
it freez at starting syslogd. never had a prob before and i changed
nothing since last reboot.
any idees to solve to prob.
ciao
Peter
CaT <[EMAIL PROTECTED]> writes:
> Ok. I've pondered but couldn't figure it out. Why does debian not
> use logrotate for the rotation of syslog files and stuff? It seems
> easy enough.
>
> The only possible reason I can think of is that you folks don't
> want
On 06-Dec-2000 CaT wrote:
> Ok. I've pondered but couldn't figure it out. Why does debian not
> use logrotate for the rotation of syslog files and stuff? It seems
> easy enough.
>
> The only possible reason I can think of is that you folks don't
> want syslogd re
Ok. I've pondered but couldn't figure it out. Why does debian not
use logrotate for the rotation of syslog files and stuff? It seems
easy enough.
The only possible reason I can think of is that you folks don't
want syslogd restarted after each file. But then that's easy eno
I went away for a few days, leaving my computer running (as it always is) and
I had an Eterm open in my X session. When I came back, I got this:
Message from [EMAIL PROTECTED] at Thu Nov 2 16:46:54 2000 ...
omega
FYI, omega is my computer's hostname. Now, what exactly does this cryptic
messag
..this _is_ a scsi drive, but it has not shown any signs of
screwiness [knock on wood]. Would '$ mount' show / as mounted
read-only?
CF> The sign is that / is mounted read-only, and that syslogd
CF> (which is still running) says scarf kernel: Last message
CF> repea
I have this problem periodically on a P133 with a slightly screwey scsi
root disk. It will mount / read-only, then many processes die due to being
unable to write to disk.
The sign is that / is mounted read-only, and that syslogd (which is still
running) says
scarf kernel: Last message
Quite serendipitously I discovered that the above processes had
stopped running on a potato system (i386) I have here. I noticed my
'locate' command did not seem to be returning good results, and when I
looked it was dated Oct 18. Then 'ps ax' told the Rest of the Story. A
reboot brought those thre
server. I will have to look into that more..
Thanks
-Original Message-
From: kmself@ix.netcom.com [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 19, 2000 12:49 PM
To: debian-user@lists.debian.org
Subject: Re: Syslogd
On Thu, Oct 19, 2000 at 11:36:52AM -0700, Jay Kelly ([EMAIL
Jay Kelly <[EMAIL PROTECTED]> writes:
> When I bootup my system hangs on "Starting System Log Daemon
> Systlogd" how can I troubleshot this to see whats happening? Thanks
Try to boot in single user mode, then the sysklogd won't start
automatically. To boot in a different runlevel, just append th
in debug mode from the
command line. man syslogd for more info.
Startup hangs are very often DNS resolution timeouts. What happens if
you give your system five or ten minutes to boot, does the hang clear?
--
Karsten M. Self http://www.netcom.com/~kmself
Evangelist, Opensales, Inc.
Hello All,
When I bootup my system hangs on
"Starting System Log Daemon Systlogd" how can I troubleshot this to see
whats happening?
Thanks
-BEGIN PGP SIGNED MESSAGE-
On Wed, 6 Sep 2000, David Wright wrote:
> > Message from [EMAIL PROTECTED] at Tue Sep 5 17:42:31 2000 ...
> > locust
>
> In my experience, this happens someone tries the rpc.statd buffer
> overflow exploit. I'm surprised you don't see it in syslog and messages
Quoting Noah L. Meyerhans ([EMAIL PROTECTED]):
>
> This is really weird. I've got potato running on a machine at work,
> configured pretty much the same as all my other workstation in terms of
> software. Every few days or so I get the following message broadcast out
> to all my login sessions:
-BEGIN PGP SIGNED MESSAGE-
This is really weird. I've got potato running on a machine at work,
configured pretty much the same as all my other workstation in terms of
software. Every few days or so I get the following message broadcast out
to all my login sessions:
Message from [EMAIL P
d the log file is empty still. I'd like
to
brooni >> redirect everything from 10.10.10.1 to /var/log/dsl.log
brooni >
brooni >The standard syslog doesn't support that, although I don't know about
brooni >others. If you need the separate logs you'll have to eith
ers. If you need the separate logs you'll have to either find a
syslogd replacement that does what you want or post-process based on the
host field in the logfile(s). If you're processing the logs you may
find it easier to create a catchall log that gets everything written to
it and st
On Wed, Aug 02, 2000 at 10:45:59PM -0700, [EMAIL PROTECTED] wrote
> ok, i got syslogd working it is recieving log entries from my router, now
> im curious how i would redirect those to a dedicated file? i tried various
> things in /etc/syslog.conf and the log file is empty still. I&
On Wed, 02 Aug 2000 22:45:59 PDT, "[EMAIL PROTECTED]" writes:
>ok, i got syslogd working it is recieving log entries from my router, now
>im curious how i would redirect those to a dedicated file? i tried various
>things in /etc/syslog.conf and the log file is empty still. I&
ok, i got syslogd working it is recieving log entries from my router, now
im curious how i would redirect those to a dedicated file? i tried various
things in /etc/syslog.conf and the log file is empty still. I'd like to
redirect everything from 10.10.10.1 to /var/log/dsl.log
sample log en
there
anything
bgoudi >> special i have to do to syslogd to allow this? i didnt see anything
bgoudi >
bgoudi >The default for for syslogd is not to accept messages from network
hosts.
bgoudi >Use '-r' to turn this on.
bgoudi >
bgoudi >--
bgoudi >A good name
On Tue, Aug 01, 2000 at 11:19:49PM -0700, [EMAIL PROTECTED] wrote:
> i just got a cisco675 for my dsl today and noticed it supports syslog, i
> want to get it to send log entries to one of my boxes, is there anything
> special i have to do to syslogd to allow this? i didnt see anyt
i just got a cisco675 for my dsl today and noticed it supports syslog, i
want to get it to send log entries to one of my boxes, is there anything
special i have to do to syslogd to allow this? i didnt see anything
special in the man page but i am curious if by default syslogd allows this
what is
Gregory Guthrie wrote:
>
> INIT: entering run level 2
> Starting system log daemon: syslogd
>
> and hangs...
>
Wild-ass guess based on bad reasoning and half-remembered experience:
Is it just possible you filled up a partition when you de-tarred all
that stuff? Like maybe the /var partition?
stead of /dev/hda6. The fact that you get to
> >single-user mode means that hte kernel and LILO are configured correctly.
>
> -- John, Bingo. Thanks.
>
> I now have another problem..
>
> The boot goes into
>
> INIT: entering run level 2
> Starting system log daemon
ot
> >partition. My guess is that /etc/fstab is wrong, and that it lists
> >/dev/hda1 as root instead of /dev/hda6. The fact that you get to
> >single-user mode means that hte kernel and LILO are configured correctly.
>
> -- John, Bingo. Thanks.
>
> I now have a
at hte kernel and LILO are configured correctly.
-- John, Bingo. Thanks.
I now have another problem..
The boot goes into
INIT: entering run level 2
Starting system log daemon: syslogd
and hangs...
I edited /etc/rc2.d/S10sysklogd -> /etc/init.d/sysklogd to give hello
messages, and find that i
/usr/sbin/syslogd-listfiles or use logrotate
with all those files? Is it not better to only
use logrotate if it is installed?
Thanks in advance,
Alexander
(please Cc)
--
Gott hat dir ein Gesicht geschenkt, Laecheln musst du selber.
Alexander Koch - <>< - WWJD - aka Efraim - PGP 0xE76949
The other day my system got inadvertantly reset (happens weekly around
here with all the kids) and when I rebooted the system went through
the normal fsck, deleting inodes etc. but when it got to starting
syslogd (I believe runlevel 2?) it just hung. Rebooting again (where
it hang) and all went
On Tue, Sep 07, 1999 at 12:21:21AM +0200, Pere Camps wrote:
> Hi!
>
> How can I make syslogd mail somebody an incident (aka log) when it
> happens?
There isn't support for email in syslogd, though the remote logging
feature (line with @hostname as the action in syslog.c
Hi!
How can I make syslogd mail somebody an incident (aka log) when it
happens?
TIA!
-- p.
ebx: ecx: 002f5e68 edx: 003f
> esi: edi: ebp: esp: 002f5e84
> ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> Corrupted stack page
> Process syslogd (pid: 145, process nr: 7, stackpage=002f5000)
> Stack:
0 ecx: 002f5e68 edx: 003f
esi: edi: ebp: esp: 002f5e84
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Corrupted stack page
Process syslogd (pid: 145, process nr: 7, stackpage=002f5000)
Stack: 0
The problem has been solved. But i don't know how.
I edited some network related files (that were actually wrong)
and I get the syslogd running.
thanks to all
alberto
I have almost the exact same behavior on my slink system with 2.2.10. It is
unpredictable, but yep, syslogd, and also lpd hang on bootup. However if I
wait it
out (sometimes like 10 minutes) I get a login and everything seems fine, that
includes startx. So if you find any solutions, please
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: CRITICAL: syslogd hangs
distribution: Debian slink
kernel: 2.0.36
hardware: i486dx2
package: syslogd
version : 1.3-3
config file: original
severity: critical
When invoked by INIT
1 - 100 of 149 matches
Mail list logo
