sysklogd (1.4.1-21ubuntu3) gutsy; urgency=low
* debian/rc:
* Fix syslogd to run as syslog user. Fix LP: #120085.
* Add comment that points to /etc/default/syslogd to set default options.
Fix LP: #103232.
* debian/cron.daily, debian/cron.weekly:
* Rotate logs with the correct
Thanks for your patch.
However, I would just update the comment to state that the default
configuration should be set in /etc/default/syslogd.
I wouldn't set the default SYSLOGD in the init script to use the -u
switch as this configuration needs more work to make it works correctly
(as you report
I have found further problems with syslogd, which I've reported in bug
#120085.
--
sysklogd init-script arguments [patch inside]
https://bugs.launchpad.net/bugs/103232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Sorry, I need to upload yet another version of the patchset... third
time lucky. I wasn't allowing for the possibility that
/etc/default/syslogd exists, yet doesn't set $SYSLOGD. This is mentioned
in the Debian policy manual at http://www.debian.org/doc/debian-policy
/ch-opersys.html, section 9.3.2
smaug said:
>>oh - that was what confused me in the first post ... running syslogd as root
>>may be a potential security issue, is it ?<<
I think it is. I'll flag this as a security bug.
** This bug has been flagged as a security issue
** Changed in: sysklogd (Ubuntu)
Status: Unconfirmed
** Changed in: sysklogd (Ubuntu)
Status: Rejected => Unconfirmed
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Oops, I left a debugging statement in one of the patches. Revised
patchset attached.
** Attachment added: "syslogpatch2.tar.gz"
http://launchpadlibrarian.net/8036281/syslogpatch2.tar.gz
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You received this bug notification
:) oh - that was what confused me in the first post ... running syslogd
as root may be a potential security issue, is it ?
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I still believe there is a bug, although it has changed slightly. I'm
running a very new, fresh install of feisty.
The default /etc/init.d/sysklogd has the line:
SYSLOGD="-u syslog"
The default /etc/init.d/syslogd has the line:
SYSLOGD=""
which overrides/nukes the init.d parameters.
so if I understand you right variables in init-scripts should not be
changed. Changes should be made in the "default" files.
Sorry for the misunderstanding and thank you for the explanation.
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You received this bug notificati
Paradoxically, the /etc/default files are intended for you to modify to
*change* the defaults -- so you don't need to edit the init script, and
thus risk difficult merges if the init script changes.
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You received this bug not
thank you for your reply,
yes I have such a file:
--snip--
#
# For remote UDP logging use SYSLOGD="-r"
#
SYSLOGD=""
--snap--
so it's correct that the default file is overwriting the the arguments
in the init.d-script ? isn't it better to place the default-definition
over the SYSLOGD variable in
Do you have either an /etc/default/syslogd or /etc/ltsp/syslogd file,
which can override the value of that variable (as documented in the
script)?
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You received this bug notification because you are a member of Ubuntu
Bugs, w
I can confirm this bug. I found that if you move the SYSLOGD line
containing the parameters down below the ". /lib/lsb/init-functions"
line, then it works. So something in init-functions is nuking the
SYSLOGD variable.
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You
let me try to explain it again:
--snip--
[EMAIL PROTECTED]:~$ ps aux |grep sysl
root 4523 0.0 0.1 1700 644 ?Ss 19:28 0:00 /sbin/syslogd
fmeister 29528 0.0 0.1 2884 748 pts/1R+ 21:06 0:00 grep sysl
--snap--
syslog is running as _root_ but in /etc/init.d/sysklog
that is what I've done. I've changed the variable in the script.
--
sysklogd init-script arguments
https://bugs.launchpad.net/bugs/103232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Where is it documented that you can pass the variable into the script?
If you want to change the arguments, EDIT the script and change the
SYSLOGD variable definition near the top
** Changed in: sysklogd (Ubuntu)
Status: Unconfirmed => Rejected
--
sysklogd init-script arguments
https://b
17 matches
Mail list logo
