Hi,
Ah yes, I added the symlink creation in the init script of nxlog, and
everything works now. Thanks for your help.
Regards,
Christophe
2014-09-08 19:14 GMT+02:00 Botond Botyanszki <b...@nxlog.org>:
> Hi,
>
> Creating the socket under /dev requires root privileges, if you run it as
> "nxlog" it can only create the socket where it can write, e.g.
> Uds /var/run/nxlog/devlog
> It is possible that the symlink under /dev gets wiped out during a
> reboot. In that case you can add 'ln -s ...' to the nxlog init script or
> something similar (rc.local ?) that gets called during boot.
>
> Regards,
> Botond
>
> On Mon, 8 Sep 2014 18:12:31 +0200
> Christophe L <lec.christo...@gmail.com> wrote:
>
> > Hello,
> >
> > I'm trying to use nxlog to replace rsyslog on a CentOS 6.5.
> > Rsyslog used to create the socket /dev/log. Now that it is gone, NxLog is
> > in charge of the creation of the socket, and does so if it is root.
> > However, if I specify that I want Nxlog to run under the user "nxlog",
> > Nxlog can not create the socket /dev/log :
> > ERROR couldn't bind socket /dev/log;Permission denied
> >
> > I tried to create a symlink as specified here :
> >
> https://www.mail-archive.com/nxlog-ce-users@lists.sourceforge.net/msg00103.html
> >
> > But if I reboot, no one creates /dev/log, and the symlink points to
> nothing.
> >
> > So my question is : How can I do to make nxlog drop its privilege while
> > also creating /dev/log?
> >
> > Here is my nxlog.conf file if it can be useful :
> >
> > Moduledir /usr/local/libexec/nxlog/modules
> > Pidfile /tmp/nxlog.pid
> > LogFile /var/log/nxlog.log
> > Cachedir /tmp
> > #User nxlog
> > #Group nxlog
> > LogLevel info
> > # define CERTDIR ../../../test/cert
> > define CONFDIR /tmp
> >
> > <Extension syslog>
> > Module xm_syslog
> > </Extension>
> >
> > <Input uds>
> > Module im_uds
> > # Uds /var/run/nxlog/devlog
> > Uds /dev/log
> > Exec parse_syslog_bsd();
> > FlowControl false
> > </Input>
> >
> > <Input kern>
> > Module im_kernel
> > Exec parse_syslog_bsd();
> > </Input>
> >
> > <Output fileout>
> > Module om_file
> > File "/var/log/logmsg.txt"
> > </Output>
> >
> > <Output fileout2>
> > Module om_file
> > File "/var/log/logkern.txt"
> > </Output>
> >
> > <Route 1>
> > Path uds => fileout
> > </Route>
> >
> > <Route 3>
> > Path kern => fileout2
> > </Route>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> nxlog-ce-users mailing list
> nxlog-ce-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
