On 2/22/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> On 2/22/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> >
> > What happens when you don't have /dev/console listed for kern.*? Does
> > it still log something to the console (I think so, but I'd just like
> > to be sure of that).
> >
>
> I'
On 2/22/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> I agree that we should ship a default syslog.conf, that's almost required imo.
> I'm not sure about if logrotate is required, but it would be a great addition.
> Regarding cron I've wanted one for a long time and we have had talks
> about it,
On 2/22/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
>
> What happens when you don't have /dev/console listed for kern.*? Does
> it still log something to the console (I think so, but I'd just like
> to be sure of that).
>
I'm testing multiple entries for kern.* Anyone know how to trigger
o
On 2/22/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> 2007/2/22, Carlo Calica <[EMAIL PROTECTED]>:
> > On 2/22/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
> > >
> > > Hmm.. on my new 013 system there is no /S/V/log/messages, but syslogd
> > > and klogd is running...
> > > But, now I see that
On 2/22/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> Oh yeah, forgot to submit that bug. Attached is my syslog.conf.
> Should we ship a default? If so, we should also have a rotatelogs and
> cron.
I'd be interested in having a sensible default shipped with the
recipe/package. If nothing else, i
2007/2/22, Carlo Calica <[EMAIL PROTECTED]>:
> On 2/22/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
> >
> > Hmm.. on my new 013 system there is no /S/V/log/messages, but syslogd
> > and klogd is running...
> > But, now I see that /Programs/Sysklogd/Settings does not exist!
> >
>
> Oh yeah, forg
On 2/22/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
Hmm.. on my new 013 system there is no /S/V/log/messages, but syslogd
and klogd is running...
But, now I see that /Programs/Sysklogd/Settings does not exist!
Oh yeah, forgot to submit that bug. Attached is my syslog.conf.
Should we shi
Carlo Calica wrote:
> On 2/18/07, Andy Feldman <[EMAIL PROTECTED]> wrote:
>> As Lucas said, the rule might have a syntax error. I found the syntax
>> has changed since the first time I used Udev on Gobo, so even copying
>> a rule that used to work is not guaranteed. Try running udevtest on
>> /dev/
On 2/18/07, Andy Feldman <[EMAIL PROTECTED]> wrote:
> As Lucas said, the rule might have a syntax error. I found the syntax
> has changed since the first time I used Udev on Gobo, so even copying
> a rule that used to work is not guaranteed. Try running udevtest on
> /dev/fuse: it should try to par
On 2/19/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
> > I just found this too, and was about to post you about it!
> > I found a few KERNEL="..." in 50-udev.rules too! There should be no
> > *assignments* to the KERNEL variable, it's just for checking...
> >
> > Also:
> >
> > [EMAIL PROTECTED]
Jonatan Liljedahl wrote:
> Andy Feldman wrote:
>> As Lucas said, the rule might have a syntax error. I found the syntax
>> has changed since the first time I used Udev on Gobo, so even copying
>> a rule that used to work is not guaranteed. Try running udevtest on
>> /dev/fuse: it should try to pars
Andy Feldman wrote:
> As Lucas said, the rule might have a syntax error. I found the syntax
> has changed since the first time I used Udev on Gobo, so even copying
> a rule that used to work is not guaranteed. Try running udevtest on
> /dev/fuse: it should try to parse all the rules in /S/S/udev/ru
As Lucas said, the rule might have a syntax error. I found the syntax
has changed since the first time I used Udev on Gobo, so even copying
a rule that used to work is not guaranteed. Try running udevtest on
/dev/fuse: it should try to parse all the rules in /S/S/udev/rules.d/
and warn you about an
On 2/18/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
> Jonatan Liljedahl wrote:
> > After a clean 013 install, the udev rule path isn't set properly, so it
> > finds only the rules provided by the Udev package. (So FUSE rules are
> > not found, etc...)
> >
> > Fix: add this line to /etc/udev/ud
Jonas Karlsson wrote:
> 2007/2/18, Jonatan Liljedahl <[EMAIL PROTECTED]>:
>> Jonatan Liljedahl wrote:
>>> After a clean 013 install, the udev rule path isn't set properly, so it
>>> finds only the rules provided by the Udev package. (So FUSE rules are
>>> not found, etc...)
>>>
>>> Fix: add this li
2007/2/18, Jonatan Liljedahl <[EMAIL PROTECTED]>:
> Jonatan Liljedahl wrote:
> > After a clean 013 install, the udev rule path isn't set properly, so it
> > finds only the rules provided by the Udev package. (So FUSE rules are
> > not found, etc...)
> >
> > Fix: add this line to /etc/udev/udev.conf
Jonatan Liljedahl wrote:
> After a clean 013 install, the udev rule path isn't set properly, so it
> finds only the rules provided by the Udev package. (So FUSE rules are
> not found, etc...)
>
> Fix: add this line to /etc/udev/udev.conf:
>
> udev_rules="/System/Settings/udev/rules.d"
This did
17 matches
Mail list logo
