linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Dumoulin <cdumoulin@ics-ltd.com>
To: linuxppc-embedded@ozlabs.org
Subject: "Function not implemented" error with syslogd
Date: Tue, 08 Aug 2006 09:50:13 -0400	[thread overview]
Message-ID: <44D89695.1050501@ics-ltd.com> (raw)

Hi All,
I've got an embedded linux system running on a V2Pro-based devlopment 
board, using a 2.6 kernel and ramdisk based on ELDK 4.0.
I'm trying to get syslogd running so I can log printk output to 
/var/log/messages. I'm using a Busybox syslogd that was included in the 
ELDK 4.0 ramdisk image. When I try to start syslogd, I get the following 
error:
syslogd: Couldn't get file descriptor for socket /dev/log: Function not 
implemented

The file /dev/log didn't exist, so I tried to create it with the 
following command, but that doesn't seem to make a difference:
mknod -m 660 /dev/log p

I'm assuming that syslogd does a 'socket' call, which is returning 
ENOSYS. Any ideas about what is going on, or how I can get it working, 
would be appreciated.

Regards,
Chris Dumoulin
-- 
*--Christopher Dumoulin--*
Software Team Leader

<http://ics-ltd.com/>
<http://ics-ltd.com/>

Interactive Circuits and Systems Ltd.
5430 Canotek Road
Ottawa, ON
K1J 9G2
(613)749-9241
1-800-267-9794 (USA only)

------------------------------------------------------------------------
This e-mail is private and confidential and is for the addressee only. 
If misdirected, please notify us by telephone and confirm that it has 
been deleted from your system and any hard copies destroyed. You are 
strictly prohibited from using, printing, distributing or disseminating 
it or any information contained in it save to the intended recipient.

             reply	other threads:[~2006-08-08 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 13:50 Christopher Dumoulin [this message]
2006-08-08 21:00 ` "Function not implemented" error with syslogd Christopher Dumoulin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44D89695.1050501@ics-ltd.com \
    --to=cdumoulin@ics-ltd.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).