Re: [Asterisk-Dev] is this a bug?
Chris Wade wrote: Please, we've digressed OT here - lets allow this horse to die please. As I stated in a previous post, if the -user can reproduce the crash, post it on mantis after the -user list reviews his config files. Does the horse respond to ^C ? I would think that if it is reproducible, you should get the same results with ^C as you get using the kill command to send the signal. I would consider segfaulting be a bug. The rest is wishlist. I don't type ^C or send the signal without a good reason for doing so. In so many cases the reason for doing so is due to a real bug that prevents me from shutting down the preferred way. In some of those cases I wind up having to send SIGKILL anyway. If the program is running on windows 98 I kick the reset button really hard. Paul ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [Asterisk-Dev] is this a bug?
0.59r-p1 has the fixes too. And works fine. bkw > -Original Message- > From: [EMAIL PROTECTED] [mailto:asterisk-dev- > [EMAIL PROTECTED] On Behalf Of Kenneth Long > Sent: Wednesday, January 26, 2005 1:10 AM > To: Asterisk Developers Mailing List > Subject: RE: [Asterisk-Dev] is this a bug? > > LOL! > > I think 's' is the next letter in the alphabet after > 'r'. > Its the latest release, fixing some security issue... > > http://www.gentoo.org/security/en/glsa/glsa-200501-14.xm > http://bugs.gentoo.org/show_bug.cgi?id=76862 > > > > Do not use 0.59s use 0.59r and do not install form > > portage. 0.59s (the s > > must stand for SHIT) because it doesn't work right. > > > > > > __ > Do you Yahoo!? > Meet the all-new My Yahoo! - Try it today! > http://my.yahoo.com > > > ___ > Asterisk-Dev mailing list > Asterisk-Dev@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-dev > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
Nick Bachmann wrote: Chris Wade wrote: Did any of you actually check what -c does? It runs asterisk in console mode providing a CLI instead of daemon mode where it immediately forks itself away from the controlling terminal. If you run asterisk with -c it MUST (read should according to standards) What standard is that? The standard set by 99% of apps that fit the same usage profile as asterisk (mind you there aren't that many). Most programs that offer daemon mode and console mode react the way asterisk does, it stops when you hit ^C. behave like any other linux process terminal and respond in some way to ^C (in fact if it doesn't itself, linux will - by killing the process). Huh? Ctrl+C just sends a signal (SIGINT) to the process. What the program does with the signal is up to it... if it doesn't exit, the kernel isn't going to kill it. Write a program in , don't specifically handle SIGINT, what happens? In *most* languages the process will exit - you have to specifically handle SIGINT and make sure not to exit if you don't want to exit on a SIGINT. So, technically, the kernel didn't kill it, it just sent the signal, but it still results in the kernel asking for and - typically - getting the process to exit. (semantics anyway) And as for what * does when it sees ^C, it doesn't die with any error other than a message from its input handling routines saying input was interrupted (which is what ^C is by the way - an INTERRUPT). In fact, it's a signal... the interrupt signal (that might be why they called it SIGINT :). Again, semantics. Yes its a signal, but as you stated it is the interrupt signal, therefore it is an interrupt (software sense). Please, we've digressed OT here - lets allow this horse to die please. As I stated in a previous post, if the -user can reproduce the crash, post it on mantis after the -user list reviews his config files. -Chris PS: Nick, your right on most things above - I just chose different semantics for my descriptions - maybe I shouldn't have dumbed down my words for this list - it is the -dev list after all. Kudos to you regardless. ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [Asterisk-Dev] is this a bug?
#mpg123 -v High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. Version 0.59r (1999/Jun/15). On Wed, 2005-01-26 at 07:14, Kenneth Long wrote: > --- Tuyan Ozipek <[EMAIL PROTECTED]> wrote: > > > yesterdays cvs-stable *without* any patchs > > > > Asterisk Ready. > > Asterisk Malloc Debugger Started (see > > /var/log/asterisk/mmlog) > > Beginning asterisk shutdown > > Beginning asterisk shutdown > > Executing last minute cleanups > > == Destroying any remaining musiconhold processes > > Jan 26 01:40:09 DEBUG[9342]: res_musiconhold.c:644 > > ast_moh_destroy: > > killing 9348! > > Ouch ... error while writing audio data: : Broken > > pipe > > Segmentation fault > > > > seems to be a moh/mpg321 related *crash* > > > > > mine: > bash-2.05b$ mpg123 --version > Version 0.59s-r9 (2000/Oct/27) > bash-2.05b$ > > I got a compile warning about having the wrong > release... "r9" instead of not having "r9" > > > > > __ > Do you Yahoo!? > Meet the all-new My Yahoo! - Try it today! > http://my.yahoo.com > > > ___ > Asterisk-Dev mailing list > Asterisk-Dev@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-dev > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev -- Tuyan Ozipek <[EMAIL PROTECTED]> ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [Asterisk-Dev] is this a bug?
LOL! I think 's' is the next letter in the alphabet after 'r'. Its the latest release, fixing some security issue... http://www.gentoo.org/security/en/glsa/glsa-200501-14.xm http://bugs.gentoo.org/show_bug.cgi?id=76862 > Do not use 0.59s use 0.59r and do not install form > portage. 0.59s (the s > must stand for SHIT) because it doesn't work right. > __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
Alexander Lopez wrote: ^c. = interrupt ^d = eof Etc -Original Message- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> To: 'Asterisk Developers Mailing List' Sent: Tue Jan 25 13:39:01 2005 Subject: Re: [Asterisk-Dev] is this a bug? On January 25, 2005 12:57 pm, Brian West wrote: > No its not a bug.. it will always do that if you start it with -c It's not a bug that enabling colour will "allow" asterisk to die with ^C, ^S?? If it's not a bug then why does ^C, ^S, etc. not cause * to die? -c Provide a control console on the calling terminal. Specifying this option implies -f and will cause asterisk to no longer fork or detach from the controlling terminal. -c has nothing to do with colour. See above. The CTL-c send an SIG-INT to the process thus killing it. Don't use the -c and this won't happen. You can connect to the asterisk that is running as a daemon by using asterisk -r. HTH, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
On Tue, 2005-01-25 at 10:52 -0800, Kenneth Long wrote: > thanks... but this is not the point I'm really > asking... copying is not the issue... > > I'm worried about the invalid pointer message. > > The ctrl-c crashes Asterisk in xterm. > > I wish such commands would not so easily crash it. > > Is the crash "normal" behavior? Asterisk isn't so much crashing as not eloquently exiting. By sending ctrl-c to asterisk, you are actually asking it to quit. While I cringe when I ave to use it, when you have connected to asterisk with "asterisk -r", you have to use ctrl-c to exit the connection. The trouble basically being that you are then using the asterisk executable as a specialized communications tool. > --- Steven Critchfield <[EMAIL PROTECTED]> wrote: > > > Hello -user question from a windows user. > > > > On Tue, 2005-01-25 at 09:14 -0800, Kenneth Long > > wrote: > > > I'm launching Asterisk on a xterm session. > > > I wanted to highlight some text and out of > > > habit I did a ctrl-C. That reliably and > > consistantly > > > shuts down Asterisk with a invalid pointer. > > > Same error message everytime. > > > > Ctrl-c is actually an interupt. Windows users needed > > easy to remember > > shortcuts, thats why you are used to ctrl-c. > > > > > Some other Ctrl- key sequences lock the session, > > too. > > > like ctrl-S. > > > > >From terminal days, ctrl-s is flow control stop. > > ctrl-q is what you use > > to restart from a ctrl-s. > > > > Most terminals should automatically copy on select. > > You will find unix > > traditions are full of as short as can be short > > cuts. Select implies > > copy and middle click pastes. Click select click and > > your done. > > -- > > Steven Critchfield <[EMAIL PROTECTED]> > > > > ___ > > Asterisk-Dev mailing list > > Asterisk-Dev@lists.digium.com > > > http://lists.digium.com/mailman/listinfo/asterisk-dev > > To UNSUBSCRIBE or update options visit: > > > > > http://lists.digium.com/mailman/listinfo/asterisk-dev > > > > > > > __ > Do you Yahoo!? > Yahoo! Mail - Helps protect you from nasty viruses. > http://promotions.yahoo.com/new_mail > ___ > Asterisk-Dev mailing list > Asterisk-Dev@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-dev > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev -- Steven Critchfield <[EMAIL PROTECTED]> ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
Please don't post with HTML, **ESPECIALLY** in the -dev list. On January 25, 2005 02:35 pm, Alexander Lopez wrote: > ^c. = interrupt > ^d = eof > Etc I've been using Unix for 10 years, I know what they mean. I am saying that if they *don't* cause * to crash without -c, why do they cause * to crash with -c... also why are they not being trapped and handled properly instead of literally crashing the server. -A. ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
On January 25, 2005 02:54 pm, Eric Wieling wrote: > As you can see -c means CONSOLE, not COLOR. Then why does "asterisk -vvg" spit up a CLI, and "asterisk -vvgc" spit up the same CLI in colour? :-) I will admit that lacking a '-c' does not give me a CLI, but it also gives me colour output. -A. ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [Asterisk-Dev] is this a bug?
I start asterisk with asterisk -vgc I press ctrl-c I get *CLI> Beginning asterisk shutdown Beginning asterisk shutdown Killed bkw > -Original Message- > From: [EMAIL PROTECTED] [mailto:asterisk-dev- > [EMAIL PROTECTED] On Behalf Of Kenneth Long > Sent: Tuesday, January 25, 2005 12:53 PM > To: Asterisk Developers Mailing List > Subject: Re: [Asterisk-Dev] is this a bug? > > thanks... but this is not the point I'm really > asking... copying is not the issue... > > I'm worried about the invalid pointer message. > > The ctrl-c crashes Asterisk in xterm. > > I wish such commands would not so easily crash it. > > Is the crash "normal" behavior? > > > regards, > Ken > > > --- Steven Critchfield <[EMAIL PROTECTED]> wrote: > > > Hello -user question from a windows user. > > > > On Tue, 2005-01-25 at 09:14 -0800, Kenneth Long > > wrote: > > > I'm launching Asterisk on a xterm session. > > > I wanted to highlight some text and out of > > > habit I did a ctrl-C. That reliably and > > consistantly > > > shuts down Asterisk with a invalid pointer. > > > Same error message everytime. > > > > Ctrl-c is actually an interupt. Windows users needed > > easy to remember > > shortcuts, thats why you are used to ctrl-c. > > > > > Some other Ctrl- key sequences lock the session, > > too. > > > like ctrl-S. > > > > >From terminal days, ctrl-s is flow control stop. > > ctrl-q is what you use > > to restart from a ctrl-s. > > > > Most terminals should automatically copy on select. > > You will find unix > > traditions are full of as short as can be short > > cuts. Select implies > > copy and middle click pastes. Click select click and > > your done. > > -- > > Steven Critchfield <[EMAIL PROTECTED]> > > > > ___ > > Asterisk-Dev mailing list > > Asterisk-Dev@lists.digium.com > > > http://lists.digium.com/mailman/listinfo/asterisk-dev > > To UNSUBSCRIBE or update options visit: > > > > > http://lists.digium.com/mailman/listinfo/asterisk-dev > > > > > > > __ > Do you Yahoo!? > Yahoo! Mail - Helps protect you from nasty viruses. > http://promotions.yahoo.com/new_mail > ___ > Asterisk-Dev mailing list > Asterisk-Dev@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-dev > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
On Tuesday 25 January 2005 12:39, Andrew Kohlsmith wrote: > On January 25, 2005 12:57 pm, Brian West wrote: > > No its not a bug.. it will always do that if you start it with -c > > It's not a bug that enabling colour will "allow" asterisk to die with > ^C, ^S?? If it's not a bug then why does ^C, ^S, etc. not cause * to > die? > > i.e. why does enabling colour enable these particular crashes? This > doesn't seem to be the kind of "undocumented feature" that is > conducive to a good environment. :-) c is for console, not for color (see the output of 'asterisk -h'). As the process is running in the foreground, Ctrl-C naturally interrupts the foreground process. Note that if you start asterisk in the background (i.e. without the -c option or with a startup script), then connect to it with -r or -R, Ctrl-C will not exit the main asterisk process, but only the remote console. Here ends the -user lesson on the -dev list. -- Tilghman ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
Andrew Kohlsmith wrote: On January 25, 2005 12:59 pm, Steven Critchfield wrote: Ctrl-c is actually an interupt. Windows users needed easy to remember shortcuts, thats why you are used to ctrl-c. Yes but why does ^C only interrupt asterisk when -c (colour) is given? To me this is a bug. Asterisk should either always trap these key sequences or always pass them, irrespective of your desire to see coloured console messages. Did any of you actually check what -c does? It runs asterisk in console mode providing a CLI instead of daemon mode where it immediately forks itself away from the controlling terminal. If you run asterisk with -c it MUST (read should according to standards) behave like any other linux process terminal and respond in some way to ^C (in fact if it doesn't itself, linux will - by killing the process). And as for what * does when it sees ^C, it doesn't die with any error other than a message from its input handling routines saying input was interrupted (which is what ^C is by the way - an INTERRUPT). So exactly why is this a bug? -Chris PS. below is the 'asterisk -h' from CVS-HEAD, notice the only mention of color is the '-n' option, not the '-c' option :) Asterisk CVS-HEAD-01/24/05-10:35:33, Copyright (C) 2000 - 2005, Digium. Usage: asterisk [OPTIONS] Valid Options: -V Display version number and exit -C Use an alternate configuration file -G Run as a group other than the caller -URun as a user other than the caller -c Provide console CLI -d Enable extra debugging -f Do not fork -g Dump core in case of a crash -h This help screen -i Initialize crypto keys at startup -n Disable console colorization -p Run as pseudo-realtime thread -q Quiet mode (suppress output) -r Connect to Asterisk on this machine -R Connect to Asterisk, and attempt to reconnect if disconnected -t Record soundfiles in /var/tmp and move them where they belong after they are done. -v Increase verbosity (multiple v's = more verbose) -x Execute command (only valid with -r) ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
On Tuesday 25 January 2005 12:52, Kenneth Long wrote: > thanks... but this is not the point I'm really > asking... copying is not the issue... > > I'm worried about the invalid pointer message. > > The ctrl-c crashes Asterisk in xterm. > > I wish such commands would not so easily crash it. > > Is the crash "normal" behavior? It's not a crash; it's an interrupt. You specifically asked Asterisk to interrupt, and Asterisk obeyed. If you would like to set another key to be terminal interrupt, you can. For example, bash$ stty intr ^ will change the interrupt key from Ctrl-C to ^, which might be something you'd be less likely to use. To change it back without exiting, type: 'stty intr ' -- Tilghman ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
Andrew Kohlsmith wrote: On January 25, 2005 12:59 pm, Steven Critchfield wrote: Ctrl-c is actually an interupt. Windows users needed easy to remember shortcuts, thats why you are used to ctrl-c. Yes but why does ^C only interrupt asterisk when -c (colour) is given? To me this is a bug. Asterisk should either always trap these key sequences or always pass them, irrespective of your desire to see coloured console messages. As you can see -c means CONSOLE, not COLOR. [EMAIL PROTECTED] root]# asterisk -rh Asterisk CVS-v1-0-12/08/04-11:02:07, Copyright (C) 2000-2004, Digium. Usage: asterisk [OPTIONS] Valid Options: -V Display version number and exit -C Use an alternate configuration file -G Run as a group other than the caller -URun as a user other than the caller -c Provide console CLI -d Enable extra debugging -f Do not fork -g Dump core in case of a crash -h This help screen -i Initializie crypto keys at startup -n Disable console colorization -p Run as pseudo-realtime thread -q Quiet mode (supress output) -r Connect to Asterisk on this machine -R Connect to Asterisk, and attempt to reconnect if disconnected -t Record soundfiles in /tmp and move them where they belong after they are done. -v Increase verbosity (multiple v's = more verbose) -x Execute command (only valid with -r) ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
Re: [Asterisk-Dev] is this a bug?
Umm... -c is not for color... It is for "console" connection. Please check your documentation. - Original Message - From: "Andrew Kohlsmith" <[EMAIL PROTECTED]> To: "Asterisk Developers Mailing List" Sent: Tuesday, January 25, 2005 12:41 PM Subject: Re: [Asterisk-Dev] is this a bug? On January 25, 2005 12:59 pm, Steven Critchfield wrote: Ctrl-c is actually an interupt. Windows users needed easy to remember shortcuts, thats why you are used to ctrl-c. Yes but why does ^C only interrupt asterisk when -c (colour) is given? To me this is a bug. Asterisk should either always trap these key sequences or always pass them, irrespective of your desire to see coloured console messages. -A. ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [Asterisk-Dev] is this a bug?
The same reason when you do "more somefile" and ctrl C exits that too. bkw > -Original Message- > From: [EMAIL PROTECTED] [mailto:asterisk-dev- > [EMAIL PROTECTED] On Behalf Of Andrew Kohlsmith > Sent: Tuesday, January 25, 2005 12:39 PM > To: 'Asterisk Developers Mailing List' > Subject: Re: [Asterisk-Dev] is this a bug? > > On January 25, 2005 12:57 pm, Brian West wrote: > > No its not a bug.. it will always do that if you start it with -c > > It's not a bug that enabling colour will "allow" asterisk to die with ^C, > ^S?? > If it's not a bug then why does ^C, ^S, etc. not cause * to die? > > i.e. why does enabling colour enable these particular crashes? This > doesn't > seem to be the kind of "undocumented feature" that is conducive to a good > environment. :-) > > -A. > ___ > Asterisk-Dev mailing list > Asterisk-Dev@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-dev > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
RE: [Asterisk-Dev] is this a bug?
-c Provide console CLI bkw > -Original Message- > From: [EMAIL PROTECTED] [mailto:asterisk-dev- > [EMAIL PROTECTED] On Behalf Of Andrew Kohlsmith > Sent: Tuesday, January 25, 2005 12:42 PM > To: Asterisk Developers Mailing List > Subject: Re: [Asterisk-Dev] is this a bug? > > On January 25, 2005 12:59 pm, Steven Critchfield wrote: > > Ctrl-c is actually an interupt. Windows users needed easy to remember > > shortcuts, thats why you are used to ctrl-c. > > Yes but why does ^C only interrupt asterisk when -c (colour) is given? To > me > this is a bug. Asterisk should either always trap these key sequences or > always pass them, irrespective of your desire to see coloured console > messages. > > -A. > ___ > Asterisk-Dev mailing list > Asterisk-Dev@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-dev > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-dev ___ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
