In Debian 4, it seems that the sysklogd initscript does not
check any /etc/default (like sysconfig in redhat) file,
and in fact sets SYSLOGD=""
SO I gather I need to edit the initscript if I want to change
syslogd's commandline params, or is there some other local
mechanism that al
On Wed, Sep 3, 2008 at 12:30 PM, Jabka Atu <[EMAIL PROTECTED]> wrote:
> Good day ,.
>
> I'm searching for a way to stop the escaping of rsyslog for example if i
> send a message that include \n it is described as "#012" :
>
> /**
> * Lets test the newlinje issues and the Length
> */
>
> #include
Good day ,.
I'm searching for a way to stop the escaping of rsyslog for example if i
send a message that include \n it is described as "#012" :
/**
* Lets test the newlinje issues and the Length
*/
#include
#include
#include
#include
int main(void) {
char * foo ;
int i = 0;
foo = (char
know
iptables is working.
$ dpkg -l sysklogd | grep ii
ii sysklogd 1.4.1-17 System Logging Daemon
$ grep '\-m 0' /etc/init.d/sysklogd
SYSLOGD="-m 0 -a /chroot/named/dev/log"
When I issue a `/etc/init.d/sysklogd restart`, I see this in /var/log/messages
Jul 21 14:40:0
On Tue, Feb 10, 2004 at 11:35:33AM +, David Goodenough wrote:
> Why do the cron.daily/weekly sysklogd script exit doing nothing if the
> /usr/share/doc/sysklogd directory not exist? It rightly checks that
> the binaries it needs are there, but the doc directory is purely
> d
Why do the cron.daily/weekly sysklogd script exit doing nothing if the
/usr/share/doc/sysklogd directory not exist? It rightly checks that
the binaries it needs are there, but the doc directory is purely
documentation.
I hit this on a stripped down emebedded installation which I
noticed was
Hello All,
I saw this before, but forgot the solution.
My Debian/testing just spends minutes in starting sysklogd, when there's
no network interface presents.
The similar things happened to sendmail, xdm also.
Thanks a lot!
Regards,
Dongxu Li
--
To UNSUBSCRIBE, email to [EMAIL PROT
Quoting Christopher S. Swingley <[EMAIL PROTECTED]>:
> OK, I'm going crazy here trying to get iptables to log packets to a
> file called /var/log/kern.info.
> What am I missing? And what is the right procedure to clear a log
> without causing sysklogd / klogd to choke
-/var/log/kern.info
But /var/log/kern.info is empty:
-rw-r-1 root adm0 Jul 30 10:04 /var/log/kern.info
I've stopped and started /etc/init.d/sysklogd and /etc/init.d/klogd
multiple times (and in various orders), as well as re-running iptables.
I've also tri
are there any preferences of sysklogd vs. msyslog?
--
Johannes
Krzys Majewski wrote:
> This the potato sysklogd and a noflushd compiled from the
> sources in woody.
> Presumably the problem is noflushd logging a "Spinning
> down..." message, which gets flushed to the hard drive, heh.
> Now, I've prefixed all the file
Noflushd spins the disk up immediately after spinning it
down, unless I do a etc/init.d/sysklogd stop.
This the potato sysklogd and a noflushd compiled from the
sources in woody.
Presumably the problem is noflushd logging a "Spinning
down..." message, which gets flushed to the hard
Sorry to keep replying to my own posts but I have sysklogd installed
now. The thing I did to get around the errors was an accident. Instead
of going into dselect and selecting sysklogd to install, I ran dselect
again and skipped selecting (I had previously done that) and went strait
to install
Ok, I left things last night late and am back at it. I booted up today
and tried reinstalling sysklogd again. This time dselect tells me,
Bareword found where operator expected at -e line 1, near "/var/run"
(Missing operator before run?)
syntax error at -e line 1, near
I removed my sysklogd package with dselect off my Slink system in order
to fix a screw up I did. At any rate now when I try and install
sysklogd with dselect I get the following errors:
syntax error at -e line 1, near "startup links for "
Bareword found where operator expected at -e li
?SJun14 0:00
/sbin/syslogd
root 32683 0.1 0.5 1404 760 ?SJun14 0:00
/sbin/klogd
gateway:/# ls -l /dev/log
ls: /dev/log: No such file or directory
Martin Schulze wrote:
>
> [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > For some reason sysklogd i
For some reason sysklogd is acting up on me. Klog starts up fine, but
syslog complains about /dev/log: Invalid Argument. Why?? I've looked
for
hours, but couldn't find why. /dev/log is named pipe that is supposed
to
be created by syslog. I've tried removing & purging &
Here is info I found on the redhat.com system about the sysklogd Hack. Is
anyone working on a fix for this?
Thanks,
Ken Rea
--
Package: Sysklogd
Updated: 01-Apr-1999
Problem:
(01-Apr-1999):Security Fix
An
able to boot up from my rescue disk and chroot to my system and
> log in as root, but was not able to do it if I booted w/o the rescue disk. Do
> you know how the sysklogd was able to stop all login's, su's and my postgre?
Thus - root logins, su's and (I guess postgresql) c
and chroot to my system and
log in as root, but was not able to do it if I booted w/o the rescue disk. Do
you know how the sysklogd was able to stop all login's, su's and my postgre?
Bill
On Sat, 17 Oct 1998, Bob Nielsen wrote:
>The latest slink updat
On Wed, 21 Oct 1998, Pete Harlan wrote:
> > The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
> > installed it and could no longer become root. If you have installed it,
>
> Perhaps then a new version should be uploaded; this version would fail
> during
> The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
> installed it and could no longer become root. If you have installed it,
Perhaps then a new version should be uploaded; this version would fail
during install with a brief explanation, so we don't have to hear
peopl
Quoting Mitch Blevins ([EMAIL PROTECTED]):
> Max wrote:
> > Is the latest version of sysklogd in slink (-30) OK now? I saw all
> > the warning about -29 and I'm hoping that those bugs were fixed.
> >
> > Thanks,
> > Max
>
> sysklogd seems t
Mitch, check /etc/syslog.conf and see what it does w/ ppp. You may need to
edit it.
On 19-Oct-98 Mitch Blevins wrote:
> Max wrote:
>> Is the latest version of sysklogd in slink (-30) OK now? I saw all
>> the warning about -29 and I'm hoping that those bugs were fixed.
>&
Max wrote:
> Is the latest version of sysklogd in slink (-30) OK now? I saw all
> the warning about -29 and I'm hoping that those bugs were fixed.
>
> Thanks,
> Max
sysklogd seems to be working for me with -30.
However, the ppp.log hasn't been updated since th
On 19-Oct-98 Max wrote:
> Is the latest version of sysklogd in slink (-30) OK now? I saw all
> the warning about -29 and I'm hoping that those bugs were fixed.
>
Version -30 has been reported safe.
Is the latest version of sysklogd in slink (-30) OK now? I saw all
the warning about -29 and I'm hoping that those bugs were fixed.
Thanks,
Max
On Sat, 17 Oct 1998, Bob Nielsen wrote:
> The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
> installed it and could no longer become root. If you have installed it,
> you will need to boot with your rescue disk (you do have one, don't you?)
> and either disabl
Bob Nielsen wrote:
> The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
> installed it and could no longer become root. If you have installed it,
> you will need to boot with your rescue disk (you do have one, don't you?)
> and either disable sysklogd (chm
The latest slink update to sysklogd 1.3-29 is SERIOUSLY broken. I
installed it and could no longer become root. If you have installed it,
you will need to boot with your rescue disk (you do have one, don't you?)
and either disable sysklogd (chmod -x /etc/init.d/sysklogd) or install the
On 19 Aug 1997, Greg Stark wrote:
> # /etc/init.d/sysklogd start
> Starting /sbin/syslogd...
> /etc/init.d/sysklogd: line 38: 200 Interrupt start-stop-daemon
> --start --verbose --exec /sbin/syslogd $SYSLOGD
> Starting /sbin/klogd...
I just noticed the other day t
it doesn't seem to cause any negative effects but i can't find the
string "Interrupt" in either the bash binary or the start-stop-daemon binary
so i'm a little confused about where the message is coming from.
# /etc/init.d/sysklogd start
Starting /sbin/syslogd...
/etc/i
print = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72
--
On Fri, 23 May 1997, A.D.Y. Cheng wrote:
:Hello,
:
:I have just upgraded my Debian 1.2 to frozen disturbution. So far, there
:is no problem. However, when I reboot the machine, the machine stops for a
:few seconds after launching sysklog
t; >
> > --alex--
> >
>
> You hit the nail on the head and fixed my problem. I was using dpkg
> (1.4.0.14) and this was causing the problem. I purged and reinstalled
> sysklogd (-15 package) using dpkg (1.4.0.8) and all was well. No more
> core dumps and segmentatio
On Fri, 9 May 1997, Alex Romosan wrote:
> i think the problem is with the latest dpkg packages (1.4.0.14). i've
> downgraded to 1.4.0.8 from unstable and it works fine. it seemed to
> have worked fine up until 1.4.0.13 but i could be wrong.
Along these lines, does anybody know why syslogd in pack
d and fixed my problem. I was using dpkg
(1.4.0.14) and this was causing the problem. I purged and reinstalled
sysklogd (-15 package) using dpkg (1.4.0.8) and all was well. No more
core dumps and segmentation faults. Thanks bunches!
Cheers,
Victor
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail
i think the problem is with the latest dpkg packages (1.4.0.14). i've
downgraded to 1.4.0.8 from unstable and it works fine. it seemed to
have worked fine up until 1.4.0.13 but i could be wrong.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the min
sysklogd used to work fine. Recently it has started dumping core. I
purged and reloaded the -15 version of the package and it still does the
same thing.
Here is the error message during boot (runlevel 2):
Starting system log daemon: syslogd klogd/etc/init.d/sysklogd: line
51: 429
The latest sysklogd (syslogd) takes 10 seconds to load at boot.
Is this normal? Why the change? It used to be negligible.
Signed,
Curious in Massachusetts
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
>>>>> "Mikael" == Mikael Hallendal <[EMAIL PROTECTED]> writes:
Mikael> Hi! Why is it that the new sysklogd in 'unstable' dependens
Mikael> on an old bash and not on the new one?
Mikael> Is there any packages that dependes on bash 2.0-2 or
Siggy Brentrup writes:
> > Package: bash
> > Version: 2.0-2
> >
> > Package: sysklogd
> > Version: 1.3-12
> >
> > on my system, and running `sysklogd start' I see
> >
> > # ./sysklogd start
> > starting /sbin/syslogd ...
> &
Hi!
Why is it that the new sysklogd in 'unstable' dependens on an old bash and not
on the new one?
Is there any packages that dependes on bash 2.0-2 or is it just to downgrade
it to the one in section stable so that I can get sysklogd working
As explained when I first raised this question on gnu.bash.bug, the
problem is that sysklogd sends an interrupt signal to it's parent.
Bash used to just ignore this, now it prints a warning message.
sysklogd should be told not to do this. You can ignore the message.
--
TO UNSUBSCRIBE FROM
On Wed, 12 Jun 1996, Richard Lovison wrote:
> I just discovered that my system logging utilities stopped functioning two
> days ago after I did some upgrades. I attempted to reinstall sysklogd
> 1.3-6 but received the following error message:
>
> warning: /etc/init.d/sysklog
I just discovered that my system logging utilities stopped functioning two
days ago after I did some upgrades. I attempted to reinstall sysklogd
1.3-6 but received the following error message:
warning: /etc/init.d/sysklogd doesn't exist during rc.d setup. Error
processing sysklogd
I
Richard Lovison writes ("sysklogd upgrade"):
> I recently upgraded from syslogd 1.3-2 to sysklogd 1.3-6 manually using
> dpkg. When I started dselect I was informed that syslogd and sysklogd were
> in conflict, the configuration files for syslogd were still on the system.
>
I recently upgraded from syslogd 1.3-2 to sysklogd 1.3-6 manually using
dpkg. When I started dselect I was informed that syslogd and sysklogd were
in conflict, the configuration files for syslogd were still on the system.
I proceeded to purge syslogd but was informed I couldn't because it
Hi folks!
I'll upload a new bugfixed release to master later.
Format: 1.5
Date: Tue May 28 00:58:45 MET DST 1996
Package: sysklogd
Version: 1.3-6
Section: base
Priority: required
Essential: yes
Distribution: unstable
Architecture: i386
Depends: libc5
Conflicts: syslogd
Rep
Hi folks!
I'll upload a new bugfixed release to master later.
Format: 1.5
Date: Thu May 23 20:29:26 MET DST 1996
Package: sysklogd
Version: 1.3-5
Section: base
Priority: required
Essential: yes
Distribution: unstable
Architecture: i386
Depends: libc5
Conflicts: syslogd
Rep
ead of the traditional TakeConsole/GiveConsole
scripts run by xdm? Is there a pressing reason?
Kenny.
>
> Hello, Im having a slight problem with the newest sysklogd from the
> unstable tree. I upgraded to 1.3-2 and now My named pipe /dev/xconsole
> doesnt work from boot (I have
Hello, Im having a slight problem with the newest sysklogd from the
unstable tree. I upgraded to 1.3-2 and now My named pipe /dev/xconsole
doesnt work from boot (I have to HUP the syslogd to make it start logging
to /dev/xconsole)
The permissions on /dev/xconsole are
prw-r--r-- 1
51 matches
Mail list logo
