From: "Randy.Dunlap" <rddunlap@osdl.org>
To: sounak chakraborty <sounakrin@yahoo.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: syslog with syscall3
Date: Tue, 11 Jan 2005 08:34:21 -0800 [thread overview]
Message-ID: <41E4000D.1010708@osdl.org> (raw)
In-Reply-To: <20050111121248.67799.qmail@web53306.mail.yahoo.com>
sounak chakraborty wrote:
> dear sir,
> i am facing some problem when i want to retrieve the
> lines of
> information from the log file i.e from /var/log/messages
> i am using syslog function with syscall3 macro.it is
> showing the output
> correctly but whenever i am declaring the structures
> of sockets it is showing segmentation fault
Are there any oops messages in the kernel log?
Please post your source code (it is userspace or in-kernel?).
TIA.
> how to correctt it
> is it so that my syscall 3 macro changing the program
> to kernel mode
> and all the socket functions are not in or different
> in kernel mode ?
> then what will be the possible solution if i want t
> retrieve the information from logfile and send it to a file.
> thanks in advance
> sounak
--
~Randy
prev parent reply other threads:[~2005-01-11 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 12:12 syslog with syscall3 sounak chakraborty
2005-01-11 16:34 ` Randy.Dunlap [this message]
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=41E4000D.1010708@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sounakrin@yahoo.co.in \
/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