WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: how to extend the existing log files (daemon etc.) ?  (Read 3283 times)

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
how to extend the existing log files (daemon etc.) ?
« on: May 23, 2013, 03:45:13 PM »
Hello,
I created a file /etc/syslog.conf with the line "daemon.* /var/log/daemon.log" with the hope a daemon.log would be created for any daemon started (pppd etc.). Is it the way how to create new log files in TinyCore?
Thanks.
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: how to extend the existing log files (daemon etc.) ?
« Reply #1 on: May 23, 2013, 03:58:48 PM »
Code: [Select]
BusyBox v1.20.2 (2012-08-07 01:31:01 UTC) multi-call binary.

Usage: syslogd [OPTIONS]

System logging utility
(this version of syslogd ignores /etc/syslog.conf)

...which implies there must be another version not ignoring that config file...  ;)
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: how to extend the existing log files (daemon etc.) ?
« Reply #2 on: May 23, 2013, 04:12:56 PM »
You could try and install inetutils-servers.tcz and see if that does what you want.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

aus9

  • Guest
Re: how to extend the existing log files (daemon etc.) ?
« Reply #3 on: May 23, 2013, 08:50:52 PM »
I don't use pppd I have a working ethernet modem/router

maybe someone can make sense of this, assuming you have syslog bootcode

Code: [Select]
strings /usr/local/sbin/pppd | grep log
getlogin
openlog
closelog
syslog
setlogmask
reopen_log
pap_logout_hook
logwtmp
log_default
dbglog
tdb_logging_function
end_pr_log
log_to_fd
init_pr_log
uselogin
Don't output passwords to log
Show password string in debug log messages
@login
/var/log/lastlog
user %s logged in
login failed
No secret found for PAP login
unable to open user login data file %s
unable to read user login data file %s
Can't open log file %s: %m
logfile
nolog
nologfd
Set logical name for link
Append log messages to this file
Send log messages to this file descriptor
Don't send log messages to any file
Don't send log messages to any file descriptor
/var/log/wtmp
E=646 Restricted logon hours

/var/log/lastlog + /var/log/wtmp suggests look there first?

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: how to extend the existing log files (daemon etc.) ?
« Reply #4 on: May 24, 2013, 04:18:04 PM »
the syslog bootcode gave a good start. By using correct pppd debug/log options (see  http://ppp.samba.org/pppd.html  ) then I was not blind anymore in myking my pppd setups.
THANKS.
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: how to extend the existing log files (daemon etc.) ?
« Reply #5 on: May 24, 2013, 04:41:53 PM »
All the syslog bootcode does is executing /sbin/syslogd & /sbin/klogd (busybox) at boot time.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)