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 Bookworm
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, Devrin Talen dc...@cornell.edu 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):
On 2014-08-29, Curt cu...@free.fr 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
Am 29.08.2014 10:24, schrieb Curt:
On 2014-08-29, Devrin Talen dc...@cornell.edu 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
On 2014-08-29, Michael Biebl bi...@debian.org 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.
David Christensen dpchr...@holgerdanske.com 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
: 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
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 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
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 started to
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
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
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
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 to drop out
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 to check
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 files
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 directly;
It
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 error
Being USB volumes
On Sat, 16 Jun 2012 17:13:26 + (UTC) Camaleón noela...@gmail.com
suggested this:
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
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 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
On Fri, 15 Jun 2012 14:21:00 +0200 Alberto Fuentes
alberto.fuen...@qindel.com suggested this:
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
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
Seems to be more funny
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 systems:
Message from syslogd@nomad at Jun 16 08
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/sdd1 ?
Also,
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
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
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:
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 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-script and rotate the syslog
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
In /var/log/messages the followinglines
are apprearing:
Date Time machine name -- MARK
--
Date Time machine name -- MARK
--
Date Time machine name -- MARK
--
I'm using the following command, belowto get
rid of them, but i'm getting an error message: syslogd: no process killed.
-Bash
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:
SYSLOGD=-m 0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
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 follow
Hola,
alguien con Debian unstable aka Sid? Tengo ahora mismo actualizado el
equipo y cuando lo arranco se queda parado un buen rato durante el
arranque del demonio de syslogd. Aún así arranca, pero se queda parado
bastante tiempo ahí ... Si paro y rearranco de nuevo el servicio dentro
del sistema
El 28/06/05, v1k1ng0[EMAIL PROTECTED] escribió:
Hola,
alguien con Debian unstable aka Sid? Tengo ahora mismo actualizado el
equipo y cuando lo arranco se queda parado un buen rato durante el
arranque del demonio de syslogd. Aún así arranca, pero se queda parado
bastante tiempo ahí ... Si paro
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 downloading the 'Debian Installer
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 subscription volume which I
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 unsupported, then you
should compile your own
Bonjour à tous,
Je désirerais savoir si on peut logger au centième de seconde près.
Si quelqun a une info.
Merci.
On Mon, Nov 15, 2004 at 01:46:58PM +0100, [EMAIL PROTECTED] wrote:
Je désirerais savoir si on peut logger au centième de seconde près.
Si quelqun a une info.
Pas avec les fonctions de syslog tout seul, pour autant que
je sache. Par contre rien ne t'empêche d'utiliser
gettimeofday(2) et
Kann mir keiner einen Tip geben?
Grüße
Mathias
Moin,
ich hatte vor einigen Tagen hier gepostet, weil ich bei meinen
Mailrelays tägliche Logfiles wollte. Nach langem Hin und Her hat
das auch endlich geklappt...
Nach dem Wochenende ist aber leider ein neues Problem
aufgetaucht: syslogd
Die
* Tauber, Mathias Mailing [EMAIL PROTECTED] [20-04-2004 09:32]:
Kann mir keiner einen Tip geben?
Vielleicht. ;-)
Reicht einfach das Auskommentieren der mail* Zeilen, oder
muss mehr getan werden?
Dann log er doch kein Mail mehr. Du verschweigst uns deine Config
für deine
Moin,
Reicht einfach das Auskommentieren der mail* Zeilen, oder
muss mehr getan werden?
Dann log er doch kein Mail mehr. Du verschweigst uns deine Config
für deine Mail-Logfile-Rotation. Bitte nachliefern...
also ich habe in der standard logrotate.conf das hier hinzugefügt:
snip
On 19.04.2004 14:58 Tauber, Mathias Mailing wrote:
Die wöchentliche (und wahrscheinlich auch monatliche) Ausführung
hat zur Folge, dass auf einmal *.log.0 Dateien entstehen, die
einen Zeitraum von 22 Minuten abdecken. Ich habe jetzt schon die
man-Page zu syslogd gelesen, aber geholfen hat die
Die wöchentliche (und wahrscheinlich auch monatliche) Ausführung
hat zur Folge, dass auf einmal *.log.0 Dateien entstehen, die
einen Zeitraum von 22 Minuten abdecken. Ich habe jetzt schon die
man-Page zu syslogd gelesen, aber geholfen hat die mir nicht
wirklich.
Hat wahrscheinlicher eher etwas mit
* Tauber, Mathias Mailing [EMAIL PROTECTED] [20-04-2004 10:59]:
Dann log er doch kein Mail mehr. Du verschweigst uns deine Config
für deine Mail-Logfile-Rotation. Bitte nachliefern...
also ich habe in der standard logrotate.conf das hier hinzugefügt:
Tauber, Mathias Mailing wrote on 20.04.2004 (d.m.y):
ich hatte vor einigen Tagen hier gepostet, weil ich bei meinen
Mailrelays tägliche Logfiles wollte. Nach langem Hin und Her hat
das auch endlich geklappt...
Nach dem Wochenende ist aber leider ein neues Problem
aufgetaucht: syslogd
also ich habe in der standard logrotate.conf das hier hinzugefügt:
~~~
Das würde bedeuten, das die Rotation 2 mal durchgeführt wird.
Schau mal in /etc/logrotate.d/syslog? (bin mir bei dem Namen jetzt
nicht ganz sicher, weil es bei mir
* Tauber, Mathias Mailing [EMAIL PROTECTED] [20-04-2004 12:31]:
Das würde bedeuten, das die Rotation 2 mal durchgeführt wird.
Schau mal in /etc/logrotate.d/syslog? (bin mir bei dem Namen jetzt
nicht ganz sicher, weil es bei mir syslog-ng heißt). Hast du die
Einträge dort entfernt? Natürlich
On 20.04.2004 12:20 Tauber, Mathias Mailing wrote:
Die wöchentliche (und wahrscheinlich auch monatliche) Ausführung
hat zur Folge, dass auf einmal *.log.0 Dateien entstehen, die
einen Zeitraum von 22 Minuten abdecken. Ich habe jetzt schon die
man-Page zu syslogd gelesen, aber geholfen hat die mir
:
# snip #
hdphdmr01:~# cat /etc/cron.weekly/sysklogd
...
cd /var/log
for LOG in `syslogd-listfiles --weekly`
do
if [ -s $LOG ]; then
savelog -g adm -m 640 -u root -c 4 $LOG /dev/null
fi
done
...
# snip #
Aus der manpage von savelog:
...
For files that do exist and have
* Tauber, Mathias Mailing [EMAIL PROTECTED] [20-04-2004 13:33]:
Stimmt Ihr mir zu, und wenn ja, könnt Ihr mir eine
elegante Variante zeigen?
Ich kenne die manpage von syslogd-listfiles nicht.
Was hältst du von 'apt-get install syslog-ng' :-)
Gruss Uwe
pgp0.pgp
Description: PGP
On 20.04.2004 13:33 Tauber, Mathias Mailing wrote:
Ich habe leider bisher nicht rausgefunden, wie ich diese
ändern kann. Ich vermute auch, dass das gar nicht geht,
ohne das ich das Logging generell abschalte.
Daher macht es für mich am meisten Sinn, wenn ich
in der for-Schleife eine Abfrage
Moin,
ich hatte vor einigen Tagen hier gepostet, weil ich bei meinen
Mailrelays tägliche Logfiles wollte. Nach langem Hin und Her hat
das auch endlich geklappt...
Nach dem Wochenende ist aber leider ein neues Problem
aufgetaucht: syslogd
Die wöchentliche (und wahrscheinlich auch monatliche
hello
Jak zmusic syslogd do logowania pakietow wylapanych z firewalla na
iptables ?? mam z tym problem - np. pobieram log jak ponizej i widze ze
pakiety przechodza przez ta regulke ale ani w /var/log/syslog ani w
kern.log nic nie widac ...
/sbin/iptables -A syn-flood -j LOG --log-level debug
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:
various snips
Message from [EMAIL PROTECTED] at Sun Mar 7 01:27:17 2004 ...
dhunt kernel: MCE: The hardware reports a non fatal, correctable
incident
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
Hallo
Johannes Meyerle ([EMAIL PROTECTED]) wrote:
Hallo, hab nach n Update schwierigkeiten mit dem package
Wie kann ich das alte wohl nicht funktionierende package loswerden und
das neue installieren?
[...]
perl: warning: Setting locale failed.
perl: warning: Please check that your locale
locale: No such file or directory
(Reading database ... 121373 files and directories currently installed.)
Preparing to replace inetutils-syslogd 2:1.4.2+20030703-4 (using
.../inetutils-syslogd_2%3a1.4.2+20030703-5_i386.deb) ...
Stopping system log daemon: invoke-rc.d: initscript inetutils-syslogd
KorHeve wrote:
Bonjour à tous,
Depuis quelque temps, j'ai des petits soucis avec syslog.
Lors du boot du PC, les demons sont bien présents :
root 398 0.0 0.1 1288 560 ?S11:35 0:00 /sbin/syslogd
root 410 0.0 0.3 1944 1192 ?S11:35 0:00 /sbin/klogd
Bonjour à tous,
Depuis quelque temps, j'ai des petits soucis avec syslog.
Lors du boot du PC, les demons sont bien présents :
root 398 0.0 0.1 1288 560 ?S11:35 0:00 /sbin/syslogd
root 410 0.0 0.3 1944 1192 ?S11:35 0:00 /sbin/klogd
mais aucun message
in mein /var/log schaue, sehe ich, dass alles schön rotiert
wird.
Laut den Scripten /etc/cron.{daily,weekly}/sysklogd werden alle
logfiles rotiert, die die Befehle
syslogd-listfiles
und
syslogd-listfiles --auth
ausgeben. Wenn ich das an der Console angebe, spuckt der aber nur
folgendes aus
Scripten /etc/cron.{daily,weekly}/sysklogd werden alle
logfiles rotiert, die die Befehle
syslogd-listfiles
und
syslogd-listfiles --auth
[..]
Die zwei in /etc/cron.daily, in /etc/cron.weekly aber
syslogd-listfiles --weekly.
cu andreas
--
Häufig gestellte Fragen und Antworten
schaue, sehe ich, dass alles schön rotiert
wird.
Laut den Scripten /etc/cron.{daily,weekly}/sysklogd werden alle
logfiles rotiert, die die Befehle
syslogd-listfiles
und
syslogd-listfiles --auth
[..]
Die zwei in /etc/cron.daily, in /etc/cron.weekly aber
syslogd-listfiles --weekly
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
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-mail: [EMAIL
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?
NN
Moin,
um von Clientmaschinen auf meinen Server loggen zu können setzte ich in
/init.d/sysklogd den Parameter SYSLOGD=-rm 0.
Nach dem Neustart des Daemons läuft er Amok, folgende Einträge in der
/var/log/messages und /var/log/syslog:
Aug 29 16:00:32 parsley syslogd 1.4.1#10: restart (remote
Bonsoir,
Je viens de passer une machine sous patate d'un noyau 2.2.19 à 2.4.18.
J' au deux problèmes quand je boote sur le 2.4:
1) syslogd met bien...30s à se lancer, sans me laisser de trace particulière
dans
les logs. Le reste de l'init se passe très bien.
2) quand j'arrête la bécane, le
Le Fri, Jul 12, 2002 at 01:23:21AM +0200, [EMAIL PROTECTED] ecrit :
1) syslogd met bien...30s à se lancer, sans me laisser de trace particulière
dans
les logs. Le reste de l'init se passe très bien.
Je pense à un probleme de resolution de noms (DNS)
Sinon, NFS stoque des donnees dans des
Hartmut Figge schrieb:
[Andreas Behnert]:
auf Woody fehl. Das Problem ist wie schon geschrieben, daß ein
syslogd-listfiles -a die x1200.log gar nicht anzeigt und diese
deswegen auch nicht rotiert wird, doch warum nur???
Soll ich's Dir sagen? War ganz interessant. Das 'warum' habe
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
Mahlzeit!
Habe das Problem daß ein Logfile nicht rotiert wird. Das Skript
/etc/cron.daily/sysklogd ruft syslogd-listfiles auf und syslogd-listfiles
liefert eine Liste aller zu rotierender Logfiles.
Die /etc/syslog.conf sieht so aus:
~~snip~~
.
.
[Standard-Woody-Einträge]
.
.
local0
[Andreas Behnert]:
local0.*-/var/log/x1200.log
*.*,local0.none/dev/tty12
Facility local0 ist ein Router, d.h. der syslogd läuft mit remote
reception. Ein Aufruf von syslogd-listfiles -a liefert nun alles
mögliche, nur leider nicht die /var/log/x1200.log ...
# /etc
Hartmut Figge schrieb:
[Andreas Behnert]:
local0.*-/var/log/x1200.log
*.*,local0.none/dev/tty12
Facility local0 ist ein Router, d.h. der syslogd läuft mit remote
reception. Ein Aufruf von syslogd-listfiles -a liefert nun alles
mögliche, nur leider nicht
[Andreas Behnert]:
auf Woody fehl. Das Problem ist wie schon geschrieben, daß ein
syslogd-listfiles -a die x1200.log gar nicht anzeigt und diese
deswegen auch nicht rotiert wird, doch warum nur???
Soll ich's Dir sagen? War ganz interessant. Das 'warum' habe ich nicht
weiter verfolgt, das
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
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
with
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 you think?
--
Best
A veces me ha pasado que después de reiniciar Debian, y creo que sólo
cuando previamente el sistema tuvo errores que requirieron pasarle un
fsck (por ejemplo cuando se pierde la corriente), el inicio se detiene
justo después de iniciar syslogd. Aunque puedo escribir no hay
terminales abiertas y el
Dr. Aldo Medina wrote:
A veces me ha pasado que después de reiniciar Debian, y creo que sólo
cuando previamente el sistema tuvo errores que requirieron pasarle un
fsck (por ejemplo cuando se pierde la corriente), el inicio se detiene
justo después de iniciar syslogd. Aunque puedo escribir
On Wed, 12 Sep 2001, Dr. Aldo Medina wrote:
A veces me ha pasado que después de reiniciar Debian, y creo que sólo
cuando previamente el sistema tuvo errores que requirieron pasarle un
fsck (por ejemplo cuando se pierde la corriente), el inicio se detiene
justo después de iniciar syslogd
después de iniciar syslogd. Aunque puedo escribir no hay
terminales abiertas y el tengo que usar sys-rq para remontar sólo
lectura y reiniciar. Al reinicio y las veces subsecuentes todo es
normal. ¿Alguien tiene una idea de que será lo que está pasando? Gracias
por adelantado.
El syslogd
Por algun motivo una de las maquinas no funciona, es decir, yo le pongo
que envie los mensajes del syslog a una maquina y dicho trafico no parece
llegar.
Por defecto syslogd no escucha a otras maquinas. Tiene que ser arrancado con
la opcion -r
existe una herramienta que conecte a un
Hola, estoy haciendo unas pruebas con syslog, estoy poniendo el servicio
de syslog centralizado en una maquina.
Por algun motivo una de las maquinas no funciona, es decir, yo le pongo
que envie los mensajes del syslog a una maquina y dicho trafico no parece
llegar. Creo que puede ser cosa del
: 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 guys??
--
Leonard Leblanc
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
just sitting there. Eventually it does start up and everything
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 . . .
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 [EMAIL PROTECTED] http
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/runlevel.conf, if you're using
file-rc).
--
Best Regards
auth.debug
auth.debug-/var/log/cyclades.log
editei o script de inicializacao do syslogd /etc/rc2.d/S10syslogd e
ascrecentei a flag -r para aceitar logs de fora... coloquei o idente para
aceitar logs somente do meu dominio/roteador
restartei o syslogd... bem aparemtemente tudo deveria correer ok
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 did you
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 you, this
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; ?
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
|
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 \
|
1 - 100 of 190 matches
Mail list logo
