Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 444718 - app-admin/busybox-sysklogd, net-misc/busybox-ntpd, sys-apps/busybox-watchdog: integrate init.d scripts into sys-apps/busybox and punt
Summary: app-admin/busybox-sysklogd, net-misc/busybox-ntpd, sys-apps/busybox-watchdog:...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Stefan Briesenick (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-25 17:57 UTC by Andreis Vinogradovs ( slepnoga )
Modified: 2013-02-18 21:29 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Write pid files for klogd, nptd and watchdog like syslogd (0001-Write-pid-files-for-klogd-ntpd-and-watchdog.patch,1.81 KB, patch)
2012-12-05 19:11 UTC, Anthony Basile
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Andreis Vinogradovs ( slepnoga ) 2012-11-25 17:57:28 UTC
Please keyword app-admin/busybox-sysklogd on arm
Comment 1 SpanKY gentoo-dev 2012-11-26 06:01:35 UTC
these busybox "packages" shouldn't even exist nor ever have been added to the tree in the first place.  i thought i filed bugs for them, but i guess not.  so let's do it here.

the only thing these ebuilds do is install init.d scripts (and symlinks which collide with standard packages but lack proper blockers).  the init.d scripts should be integrated into the busybox ebuild and the init.d can execute `busybox sysklogd` rather than relying on `sysklogd`.
Comment 2 Anthony Basile gentoo-dev 2012-12-01 01:18:40 UTC
(In reply to comment #1)
> these busybox "packages" shouldn't even exist nor ever have been added to
> the tree in the first place.  i thought i filed bugs for them, but i guess
> not.  so let's do it here.
> 
> the only thing these ebuilds do is install init.d scripts (and symlinks
> which collide with standard packages but lack proper blockers).  the init.d
> scripts should be integrated into the busybox ebuild and the init.d can
> execute `busybox sysklogd` rather than relying on `sysklogd`.

These could be triggered by USE="syslogd ntpd watchdog" and then just do 

   use syslogd && busybox_config_option y syslogd

in src_configure() and

    if use syslogd; then
	newconfd "${FILESDIR}/syslogd.confd" "syslogd"
	newinitd "${FILESDIR}/syslogd.initd" "syslogd"
    fi

in src_install().  The init scripts would then read

   start-stop-daemon --start --quiet --exec /bin/busybox syslogd -- ${KLOGD_OPTS}


The only thing is, should we call the init script busybox-syslogd instead of syslogd so we don't have to add blocks to busybox?
Comment 3 Anthony Basile gentoo-dev 2012-12-01 03:42:51 UTC
Okay I've coded this into the busybox ebuild and the initd scripts and put it on my dev overlay for review:

http://git.overlays.gentoo.org/gitweb/?p=dev/blueness.git;a=tree;f=sys-apps/busybox;h=a315997f7a959ed5e7a120f8ccba6302b404a0b6;hb=168d9a95ba093071ff04116401aae5f8bfe82a54
Comment 4 SpanKY gentoo-dev 2012-12-01 07:13:18 UTC
(In reply to comment #2)

i don't see value in adding USE local flags for specific applets.  if people want to customize it, they can use their own .config.

the src_install step can easily check the local .config it used to build to see if the applets in question are supported and install the init.d scripts accordingly.

yes, naming the init.d busybox-<applet> is the way to go.
Comment 5 Anthony Basile gentoo-dev 2012-12-01 14:40:18 UTC
(In reply to comment #4)
> (In reply to comment #2)
> 
> i don't see value in adding USE local flags for specific applets.  if people
> want to customize it, they can use their own .config.
> 

It seems different from how we approach the other config options, but okay.  Here's the updated ebuild:


http://git.overlays.gentoo.org/gitweb/?p=dev/blueness.git;a=tree;f=sys-apps/busybox;h=9e146faca37edd9a722067fc5e1d57d3537e7d3b;hb=8d49ce780b2719114dfd4a6f356c16f9b3ec50cb

Note: I added a function busybox_has()
Comment 6 SpanKY gentoo-dev 2012-12-01 20:44:31 UTC
(In reply to comment #5)

the other reason for not going with USE flags is that user .config files override most of those USE flags (by design).  so checking it rather than USE is the right thing to do (just think about the conflicting settings users can easily get into).

as for the proposed change:
 - change "busybox_has" to "busybox_config_enabled"
 - no point in checking the return value:
   busybox_config_enabled() { grep -q "^CONFIG_$1=y" .config; }
 - don't bother checking for NTPD since FEATURE_NTPD_SERVER depends on it
 - split the busybox-sysklogd init.d script into syslogd and klogd -- only syslogd needs to provide "logger"
 - drop the "busybox-" prefix from the init filenames in the busybox/files/ dir -- just keep them when installing
 - the ssd logic in the init.d scripts can probably be simplified -- check out the latest rsyncd init.d script as an example
 - do not use braces around builtin variables (use $? not ${?})
Comment 7 Anthony Basile gentoo-dev 2012-12-02 15:55:19 UTC
(In reply to comment #6)
> (In reply to comment #5)
> 
> the other reason for not going with USE flags is that user .config files
> override most of those USE flags (by design).  so checking it rather than
> USE is the right thing to do (just think about the conflicting settings
> users can easily get into).
> 
> as for the proposed change:
>  - change "busybox_has" to "busybox_config_enabled"
>  - no point in checking the return value:
>    busybox_config_enabled() { grep -q "^CONFIG_$1=y" .config; }
>  - don't bother checking for NTPD since FEATURE_NTPD_SERVER depends on it
>  - split the busybox-sysklogd init.d script into syslogd and klogd -- only
> syslogd needs to provide "logger"
>  - drop the "busybox-" prefix from the init filenames in the busybox/files/
> dir -- just keep them when installing
>  - the ssd logic in the init.d scripts can probably be simplified -- check
> out the latest rsyncd init.d script as an example
>  - do not use braces around builtin variables (use $? not ${?})

Okay all of these points should be address in

http://git.overlays.gentoo.org/gitweb/?p=dev/blueness.git;a=tree;f=sys-apps/busybox;h=1e4a3b6ee220235119100151135758c3da12a073;hb=bb666b025c12e21696c994c9a6d52f7c59893c5c

There are two further questions:

1) Should we provide ntp-client? net-misc/ntp provides /etc/init.d/ntp-client, but interestingly enough, the actualy NTP_CLIENT is configurable.

2) I used start_stop_daemon_args="--name xxx" for all of them so that the daemon names show up without busybox in front.  I like it, but do we want that?
Comment 8 SpanKY gentoo-dev 2012-12-02 20:38:09 UTC
(In reply to comment #7)

you could provide ntp-client if you feel like coding it :)

the --name to ssd is neat, but i'm not sure if people would like it.  maybe use busybox.$name ?  or just leave it as is and see what people think.

for the pidfiles, don't chop the leading "busybox-"

otherwise, looks OK if you wanted to commit
Comment 9 William Hubbs gentoo-dev 2012-12-03 20:20:08 UTC
(In reply to comment #8)
> (In reply to comment #7)
> 
> you could provide ntp-client if you feel like coding it :)
> 
> the --name to ssd is neat, but i'm not sure if people would like it.  maybe
> use busybox.$name ?  or just leave it as is and see what people think.

I tested with Anthony, and it seams that invoking a daemon as:

busybox name

doesn't create the pid file in /var/run for the daemon, but using the --name option to s-s-d makes it work. We also tried using the --make-pidfile option to s-s-d, but this fails as well since the pid does not match the running process.

> for the pidfiles, don't chop the leading "busybox-"

We can't change the pid file names; busybox creates them not s-s-d, so they are hard coded.

> otherwise, looks OK if you wanted to commit
Comment 10 Anthony Basile gentoo-dev 2012-12-03 21:12:41 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)

> doesn't create the pid file in /var/run for the daemon, 

Only syslogd has code to write a pidfile and it is hard coded.  I don't think it would be too hard to write the code for klogd and ntpd to write pids.  And maybe even restore command line option for syslogd to make the pidfile name/file configurable.
Comment 11 SpanKY gentoo-dev 2012-12-04 00:32:01 UTC
(In reply to comment #10)

if that's how busybox behaves, then don't worry about it.  just add a note to the init.d files mentioning this.
Comment 12 Anthony Basile gentoo-dev 2012-12-04 12:27:25 UTC
Okay I committed this.  Note that the line

    epatch "${FILESDIR}"/${P}-*.patch

was causing the ebuild to fail, so I commented it out.  I assume you want it so you automatically get patching.  It might be a good idea to do

    #Automatically apply version specific patches
    if [ -f "${FILESDIR}"/${P}-*.patch ] ; then
        epatch "${FILESDIR}"/${P}-*.patch
    fi

so that we don't forget what I commented out on bump.

(Aside: I just discovered that [ -f ] allows file globbing while [[ -f ]] does not.  But don't put quotes around the wildcard else the former fails too, [ -f "*" ] does not work while [ -f * ] does.  Wierd)

Still to be done:

1) mask/punt app-admin/busybox-sysklogd and friends.

2) optionally add ntp-client

3) optionally add pidfile support to the other applets (upstream)
Comment 13 Anthony Basile gentoo-dev 2012-12-04 12:38:59 UTC
(In reply to comment #12)

> (Aside: I just discovered that [ -f ] allows file globbing while [[ -f ]]
> does not.  But don't put quotes around the wildcard else the former fails
> too, [ -f "*" ] does not work while [ -f * ] does.  Wierd)
> 

Actually this fails too if there are more than one patch file.  Its better to just do something like

    if ls "${FILESDIR}"/${P}-*.patch >/dev/null 2>&1 ; then
        epatch "${FILESDIR}"/${P}-*.patch
    fi
Comment 14 Anthony Basile gentoo-dev 2012-12-05 19:11:55 UTC
Created attachment 331566 [details, diff]
Write pid files for klogd, nptd and watchdog like syslogd

Okay this was sent upstream (or is that side stream when the maintainer has commit? :)
Comment 15 SpanKY gentoo-dev 2012-12-06 01:49:35 UTC
(In reply to comment #12)

commenting that line is fine as initial bumps of packages don't include patches anyways

(In reply to comment #14)

we'll sort this out on the upstream list.  probably need to add new config options like "CONFIG_CREATE_PID_FILES" and a "CONFIG_PID_FILE_PATH".
Comment 16 Anthony Basile gentoo-dev 2012-12-21 03:19:19 UTC
(In reply to comment #15)
> (In reply to comment #12)
> 
> commenting that line is fine as initial bumps of packages don't include
> patches anyways
> 
> (In reply to comment #14)
> 
> we'll sort this out on the upstream list.  probably need to add new config
> options like "CONFIG_CREATE_PID_FILES" and a "CONFIG_PID_FILE_PATH".

I added pidfile= to the initd for klogd, ntpd and watchdog just like syslogd.  I tested and they work as expected.

Last step when the next version of busybox is out and the ebuild is stabilized is to mask busybox-{sysklogd,ntpd,watchdog} for removal.
Comment 17 SpanKY gentoo-dev 2013-01-22 17:55:29 UTC
i've punted the other busybox-* ebuilds now
Comment 18 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-02 13:26:27 UTC
well, you forgot something relevant!

my busybox-sysklog ebuild were included in virtual/logger (and still is):

RDEPEND="|| ( app-admin/metalog
        app-admin/rsyslog
        app-admin/socklog
        app-admin/sysklogd
        app-admin/syslog-ng
        app-admin/syslogread
        app-admin/busybox-sysklogd
        sys-freebsd/freebsd-usbin
)"

Now, portage want to emerge all the time one of these sysloggers. That's odd! Please fix that. I only use the busybox-syslog on my virtual-machines, and that works great.

PLEASE FIX! Thanks!
Comment 19 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-02 13:34:36 UTC
I may add, that just adding sys-apps/busybox to virtual/logger is not a good idea, because it would break the whole purpose of this virtual (busybox is always installed).

Perhaps you should add (a dummy) use-flag to busybox: "syslogd"

then you could set:

   sys-apps/busybox[syslogd]

But that's up to you...
Comment 20 Anthony Basile gentoo-dev 2013-02-02 13:37:27 UTC
(In reply to comment #19)
> I may add, that just adding sys-apps/busybox to virtual/logger is not a good
> idea, because it would break the whole purpose of this virtual (busybox is
> always installed).
> 
> Perhaps you should add (a dummy) use-flag to busybox: "syslogd"
> 
> then you could set:
> 
>    sys-apps/busybox[syslogd]
> 
> But that's up to you...

Hmm ... I'm not sure I'd want app-admin/busybox in there as a substitute.  I would just drop the line app-admin/busybox-sysklogd.  As for it then pulling in one of the sysloggers, well of course it will if the have the virtual.  That's the point of the virtual.  If you don't want any logger, then unmerge the virtual itself.
Comment 21 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-02 13:41:48 UTC
I can't unmerge it! Other packages depend on that virtual, if they need a logger. So you REALLY have to add the busybox-logger to it. And it *IS* a replacement. I use it for ages this way and it works just perfect.
Comment 22 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-02 13:46:03 UTC
I added the busybox-logger to the end of the list, so that the full-featured loggers are prefered, but if you use the busybox-logger, then it is really a substitute and should be accepted as a "logger".
Comment 23 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-02 14:25:20 UTC
well, when I think about that problem, I think it's the best to add a "logger" use-flag to busybox, since this use-flag is already available. And then depend on sys-apps/busybox[logger].
Comment 24 SpanKY gentoo-dev 2013-02-03 05:33:19 UTC
Commit message: Drop app-admin/busybox-sysklogd as it no longer exists
http://sources.gentoo.org/virtual/logger/logger-0.ebuild?r1=1.3&r2=1.4
Comment 25 SpanKY gentoo-dev 2013-02-03 05:36:15 UTC
(In reply to comment #23)

USE=syslog should be fine since that's a standard global USE flag already
Comment 26 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-03 17:04:35 UTC
would you be so kind and add this "feature" then?

It's odd, that I have to install "metalog" (or any other logger) on my VMs, though busybox-syslogd alone works just fine.

Remember: there're packages which depend on virtual/logger, because they use the syslog facility. So I can't just unmerge virtual/logger, it will be installed again.
Comment 27 SpanKY gentoo-dev 2013-02-05 05:42:37 UTC
(In reply to comment #26)

feel free to post a patch for review

you can just as easily manage your package.provided file to do this
Comment 28 Anthony Basile gentoo-dev 2013-02-05 12:01:28 UTC
(In reply to comment #27)
> (In reply to comment #26)
> 
> feel free to post a patch for review
> 
> you can just as easily manage your package.provided file to do this

The only problem I see is that we don't do a busybox_config_option to ensure that CONFIG_FEATURE_PIDFILE=y.  (See early comments.)  USE=syslog should guarantee that busybox will provide syslog functionality.
Comment 29 SpanKY gentoo-dev 2013-02-08 08:21:20 UTC
(In reply to comment #28)

i don't think so.  if you have USE=savedconfig and you screw up/desync the other IUSE settings, then you get the pieces.
Comment 30 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-14 09:31:23 UTC
huh, I think this was messed up totally.

If you have all 3 busybox gadgets running, start-stop-daemon complains about alreaddy running processes.

It had a reason, why I made the symlinks in first place. If you change things, it would be nice to TEST IT!!


gentoo ~ # /etc/init.d/busybox-syslogd start
 * Caching service dependencies ...                                                                                                                  [ ok ]
 * Starting syslogd ...
 * start-stop-daemon: /bin/busybox is already running
 * Failed to start busybox-syslogd                                                                                                                   [ !! ]
 * ERROR: busybox-syslogd failed to start

no, it is NOT running, but "busybox ntpd" and "busybox watchdog" is running. Now other init-scripts are also not running, because of the dependency to "logger".

PLEASE FIX THIS ASAP! Thanks!

Hint: if you don't want to use symlinks, use "--name".
Comment 31 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-14 09:32:22 UTC
ahh, yes, since it is broken now, I set the importance to "high".
Comment 32 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-14 09:35:24 UTC
also "major",
Comment 33 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-14 12:46:19 UTC
please fix the init-scripts and please fix the virtual/logger problem. Otherwise *I* will fix it. All my VMs are broken now because of this change.

I'm ok with the inclusion within busybox itself. But I'm not happy how it was done. If you break things, FIX THEM! And not somewhere in remote future, but NOW. Sorry for CAPS, but I'm a little bit pissed...
Comment 34 Anthony Basile gentoo-dev 2013-02-14 13:02:50 UTC
(In reply to comment #33)
> please fix the init-scripts and please fix the virtual/logger problem.
> Otherwise *I* will fix it. All my VMs are broken now because of this change.
> 
> I'm ok with the inclusion within busybox itself. But I'm not happy how it
> was done. If you break things, FIX THEM! And not somewhere in remote future,
> but NOW. Sorry for CAPS, but I'm a little bit pissed...

Okay I understand the urgency.  Can you post your suggested fix.  To be clear, I did test this in numerous environments and it worked for me.
Comment 35 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-14 14:42:28 UTC
well, first the virtual/logger problem:

1. add a USE=syslog flag in busybox. Then add sys-apps/busybox[syslog] to the end of the list in virtual/logger. Now one can set USE=syslog and automagically the busybox installation will be a valid logger and the packages which depend on virtual/logger are happy and don't want to install e.g. metalog (first in list).

2. fix the init-script with a more precise commandline for start-stop-daemon. There're a few options. Basically we have the same problem as with perl/python daemons. The running binary is /bin/busybox (or /usr/bin/perl, etc.) and the real daemon is just a parameter (i.e scriptname, here 'ntpd', 'watchdog', 'klogd' and 'syslogd'). You can use the --name parameter, e.g. "busybox-syslogd" or something. Or use the options for interpreter-daemons (--interpreted, but this could be wrong if I read the man-page right).

If you can start/stop all 4 daemons independently w/o any problems when the others are running, you're done.

My solution was a symlink. That worked like a charm. But it should be possible without...
Comment 36 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-14 15:43:00 UTC
well, after (another) a reboot, it worked. I don't know what the reason was, at least syslogd starts again and so all the rest of my daemons. Nonetheless, using --name is a good idea and will make the init-script less error-prone.

But the virtual/logger problem still has to be fixed asap.

thanks!
Comment 37 Anthony Basile gentoo-dev 2013-02-14 18:36:40 UTC
(In reply to comment #36)
> well, after (another) a reboot, it worked. I don't know what the reason was,
> at least syslogd starts again and so all the rest of my daemons.
> Nonetheless, using --name is a good idea and will make the init-script less
> error-prone.
> 
> But the virtual/logger problem still has to be fixed asap.
> 
> thanks!

1) I'm not fixing something that isn't broken.  I tried repeatedly to reproduce your error and couldn't.  Here's what I'm getting.  As you can see, all three daemons are running and only the pid of the restarted process changes.

Please have more faith in your fellow developers that we do test these things.

hard-sixtyfour ~ # ps -A -o pid,cmd | grep busybox
 8339 /bin/busybox klogd -c 3
 8375 /bin/busybox syslogd -C128
 8413 /bin/busybox ntpd -N -p pool.ntp.org
 8509 grep --colour=auto busybox
hard-sixtyfour ~ # /etc/init.d/busybox-klogd restart
 * Stopping busybox-klogd ...                                         [ ok ]
 * Starting busybox-klogd ...                                         [ ok ]
hard-sixtyfour ~ # ps -A -o pid,cmd | grep busybox
 8375 /bin/busybox syslogd -C128
 8413 /bin/busybox ntpd -N -p pool.ntp.org
 8530 /bin/busybox klogd -c 3
 8534 grep --colour=auto busybox
hard-sixtyfour ~ # /etc/init.d/busybox-syslogd restart
 * Shutting down atd ...                                              [ ok ]
 * Stopping busybox-syslogd ...                                       [ ok ]
 * Starting busybox-syslogd ...                                       [ ok ]
hard-sixtyfour ~ #  * Starting atd ...                                [ ok ]
/etc/init.d/busyboxps -A -o pid,cmd | grep busybox
 8413 /bin/busybox ntpd -N -p pool.ntp.org
 8530 /bin/busybox klogd -c 3
 8566 /bin/busybox syslogd -C128
 8583 grep --colour=auto busybox
hard-sixtyfour ~ # /etc/init.d/busybox-ntpd restart
 * Stopping busybox-ntpd ...                                         [ ok ]
 * Starting busybox-ntpd ...                                         [ ok ]
hard-sixtyfour ~ # ps -A -o pid,cmd | grep busybox
 8530 /bin/busybox klogd -c 3
 8566 /bin/busybox syslogd -C128
 8605 /bin/busybox ntpd -N -p pool.ntp.org
 8609 grep --colour=auto busybox



2) Just to be clear, we're adding USE="syslog" to busybox-9999 as a "dummy" flag, ie its there bug it doesn't trigger anything.  Then we are adding sys-apps/busybox[syslog] to virtual/logger.  I see how this will work but I still feel a bit uneasy about a USE flag that really doesn't trigger anything in the ebuild.
Comment 38 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-15 01:07:34 UTC
ok, as long as it works, I'm happy. But trust me, it didn't start. I can't reproduce it now, but I had this problem on several of my VMs. And yes, I rebooted them twice and still had the problem. But ok, I will open a bug as soon I have this problem again. For now, just ignore it.

well, the USE-flag is not optimal, but the best solution right now. You don't want to add "sys-apps/busybox" to virtual/logger. That would render that virtual useless, because busybox is always installed. On the other hand, you have to include sys-apps/busybox somehow into virtual/logger, because it *can* be a drop-in replacement for a full-featured syslogger.

If you come up with a better idea, fine!

One idea from me: add useflags ntp, watchdog and syslog. And then install the init-scripts only, if the use-flags are used. Then you have your "a use-flag has to trigger something in the ebuild". ;-)

But I'm just fine with "a use-flag that just triggers external dependencies".

btw: I set it to normal/normal again.
Comment 39 Anthony Basile gentoo-dev 2013-02-15 01:57:58 UTC
(In reply to comment #38)
> ok, as long as it works, I'm happy. But trust me, it didn't start. I can't
> reproduce it now, but I had this problem on several of my VMs. And yes, I
> rebooted them twice and still had the problem. But ok, I will open a bug as
> soon I have this problem again. For now, just ignore it.
> 
> well, the USE-flag is not optimal, but the best solution right now. You
> don't want to add "sys-apps/busybox" to virtual/logger. That would render
> that virtual useless, because busybox is always installed. On the other
> hand, you have to include sys-apps/busybox somehow into virtual/logger,
> because it *can* be a drop-in replacement for a full-featured syslogger.
> 
> If you come up with a better idea, fine!
> 
> One idea from me: add useflags ntp, watchdog and syslog. And then install
> the init-scripts only, if the use-flags are used. Then you have your "a
> use-flag has to trigger something in the ebuild". ;-)
> 
> But I'm just fine with "a use-flag that just triggers external dependencies".
> 
> btw: I set it to normal/normal again.

Okay IUSE="syslog" was added to busybox-9999.

RDEPEND=sys-apps/busybox[syslog] was added to virtual/logger-0

I had to bump the latter to EAPI=2 from EAPI=0 for the use-dep.

Please test and reopen if its still a problem.
Comment 40 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-15 09:31:03 UTC
well, as long as it is in -9999, I can test it, but I will not run it on my VMs. That's tooooo unstable for me. So you should put IUSE="syslog" at least to ~arch.
Comment 41 Anthony Basile gentoo-dev 2013-02-15 18:25:28 UTC
(In reply to comment #40)
> well, as long as it is in -9999, I can test it, but I will not run it on my
> VMs. That's tooooo unstable for me. So you should put IUSE="syslog" at least
> to ~arch.

Okay its backported to busybox-1.21.0.
Comment 42 Stefan Briesenick (RETIRED) gentoo-dev 2013-02-15 22:47:10 UTC
thanks!
Comment 43 SpanKY gentoo-dev 2013-02-18 20:56:29 UTC
(In reply to comment #33)

you need to chill out

(In reply to comment #39)

there's kconfig options that the USE flag should directly expand into