[00:01] <ion> Left to right: open /var/log/foo for appending and replace fd 1 with it; replace fd 2 with a copy of fd 1. At that point, both file descriptors point to the file.
[00:01] <tanepiper> yea thats better, no horrible output on the idle server screen now - thanks :)
[08:12] <djszapi> How can I checkout the bazaar codebase, what is the VCS url ?
[08:12] <djszapi> http://upstart.ubuntu.com/wiki/CompilingUpstart - http://upstart.ubuntu.com/wiki/ContributingCode - did not find the information here.
[08:23] <plautrba> djszapi: On the first page is: 1. Get the code. Libnih is a utility library used by Upstart.  -> bzr branch lp:upstart
[08:23] <plautrba> djszapi: web frontend is here https://launchpad.net/upstart
[08:23] <djszapi> plautrba: that is just change the branch, but does not checkout the repository...
[08:23] <djszapi> no, webinterface is not enough for hacking...
[08:23] <plautrba>        bzr branch FROM_LOCATION [TO_LOCATION]
[08:23] <plautrba>               Create a new branch that is a copy of an existing branch.
[08:24] <djszapi> 10:23 < djszapi> plautrba: that is just change the branch, but does not checkout the repository...
[08:24] <plautrba> djszapi: have you tried it?
[08:24] <plautrba> lp:upstart is existing launchpad branch and you probably want local copy of that
[08:25] <djszapi> k, it does not work
[08:25] <djszapi> which port does it use ?
[08:27] <plautrba> it works for me http://fpaste.org/YwdF/
[08:28] <djszapi> glad to hear, but it does not help anything for me. Please try to answer my question, I am newbie at bazaar and I do not even like it.
[08:31] <plautrba> sorry, i can't help you with bazzar, i use only three commands (branch, pull, diff) but try http://doc.bazaar.canonical.com/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html
[08:31] <djszapi> pfff
[08:32] <djszapi> it is not about frikking bazaar
[08:32] <djszapi> come on I need the information which port it uses
[08:32] <plautrba> $ grep bzr /etc/services 
[08:32] <plautrba> bzr             4155/tcp                # Bazaar version control system
[08:32] <plautrba> bzr             4155/udp                # Bazaar version control system
[08:32] <djszapi> we have got a secure enough proxy, only http is enabled.
[08:32] <djszapi> ty.
[08:33] <djszapi> so I cannot checkout...
[08:33] <djszapi> so I cannot work on it then...
[08:35] <plautrba> djszapi: you can allways use tarball and apply patches
[08:35] <djszapi> where can I download the  tarball of HEAD master ?
[08:37] <plautrba> not sure if there is tarball of HEAD master but there is tarball of last release 
[08:39] <djszapi> :))))
[08:39] <djszapi> funny.
[08:40] <djszapi> there is no http way in case bazaar to clone.
[08:40] <djszapi> it is silly enuff.
[08:42] <djszapi> A general way about a git repository: http/ssh/git/ protocol availability.
[08:42] <djszapi> btw, last release does not really contain the updated codebase...
[08:42] <djszapi> nor the libnih stuff...
[08:43] <djszapi> logging.c fex.
[08:45] <plautrba> there are 6 commits in upstart after release, it's not so much work to download patches from lp and apply them locally
[08:45] <djszapi> pfff
[08:47] <djszapi> no sorry I am not gonna spend my times with things I should not deal with.
[08:47] <djszapi> I am just skippign this "patch is welcome" thingy.
[08:48] <plautrba> it's like, sorry i locked my door so i can't go walk your dog ...
[08:49] <djszapi> maybe that is why this software is abandoned
[08:49] <djszapi> and no contributors apart from Scott.
[14:32] <cchildress> hi all. i'm having trouble getting vsftpd and upstart to play nice. whenever i issue the "restart," "stop," or "status" commands on vsftpd, I get teh error "unknown instance"
[14:32] <cchildress> if i issue the "start" command it tells me vsftpd is started/starting, and gives a pid
[14:33] <cchildress> but then "sudo status vsftpd" immediately after gets "stopped/waiting"
[14:33] <cchildress> like it says it's starting, but doesn't get started
[14:33] <cchildress> any ideas? maybe i'm doing something wrong?
[14:45] <JanC> cchildress: do you use "expect fork" or "expect daemon" ?
[14:45] <JanC> it sounds like apport is looking at the wrong PID
[14:45] <JanC> upstart I mean
[14:52] <cchildress> JanC: not that i'm aware of
[14:52] <cchildress> i'm not even sure what expect is haha
[14:53] <JanC> "man 5 init" explains all stanzas you can use in upstart jobs
[14:53] <cchildress> i'll check on that
[14:54] <JanC> basically you tell upstart that there will be 1 or 2 forks to follow
[14:54] <JanC> (in future versions this should become more flexible)
[14:54] <cchildress> i'm sorry, but i'm not sure that i follow you
[14:54] <cchildress> i know what a fork is, but what is meant by upstart following them?
[14:55] <cchildress> all i really want to do, is be able to start or stop vsftpd
[14:55] <cchildress> that's all
[14:55] <cchildress> right now i can't seem to do either
[14:55] <JanC> it needs to "follow" the forks to know what the PID of the actual running process is
[14:56] <cchildress> ok
[14:56] <cchildress> yes that makes sense
[14:58] <cchildress> so are you saying that i'm getting the "unknown instance" error because it's not following the forked process correctly?
[14:59] <cchildress> ok so i read through that manpage...but what am i supposed to make of it?
[15:01] <cchildress> sorry i must seem pretty slow but i feel like i'm trying to do something so simple
[15:02] <JanC> cchildress: it seems like vsftpd has an upstart job in Ubuntu 10.10, if you want I can put it on a pastebin for you
[15:02] <cchildress> what would i do with that? place it in /etc/init?
[15:02] <cchildress> and wouldn't that already be installed on my system when i installed vsftpd?
[15:03] <JanC> are you using Ubuntu 10.10 ?
[15:04] <cchildress> JanC: no, i believe i'm sticking with 10.04 for now
[15:05] <JanC> cchildress: is there a vsftpd.conf in /etc/init/ ?  if not, 10.04 was still using a sysvinit script in /etc/init.d/
[15:07] <cchildress> fwiw, http://ubuntuforums.org/showthread.php?t=1588568
[15:07] <cchildress> yes, there is a vsftpd.conf in /etc/init
[15:09] <JanC> that you on the forums?
[15:09] <cchildress> so i see how i can keep it from running...but not how to check the status or stop it from the command line
[15:09] <cchildress> no, just someone who has similar problems
[15:11] <cchildress> i'm just trying to figure out why the standard "sudo service vsftpd stop
[15:11] <cchildress> won't work
[15:11] <cchildress> and why i can't check on the status
[15:12] <cchildress> is there something wrong in the script or conf? or am i doing something wrong?
[15:13] <JanC> vsftpd seems to start/stop/status/etc. fine on my 10.10 system
[15:13] <JanC> did you change anything in the configuration of vsftpd?
[15:14] <cchildress> no
[15:14] <cchildress> i have avoided that because i don't want to break things
[15:15] <JanC> no debug info in log files?
[15:16] <cchildress> the vsftpd.log in /var/log is blank
[15:17] <cchildress> what other log file can i check? there is not one for upstart
[15:27] <cchildress> i'm at such a loss >.<
[15:27] <cchildress> i loved the good old init.d scripts haha
[15:29] <JanC> can you start vsftpd manually?
[15:34] <cchildress> this thread has teh same problem: http://ubuntuforums.org/showthread.php?p=10361956
[15:35] <JanC> hm, that looks like vsftpd forks one more time than expected?
[15:37] <cchildress> maybe, but i don't know enough to say
[15:37] <cchildress> i'm surprised that others haven't reported this problem
[15:37] <JanC> do you also see the different PIDs like in that forum post?
[15:37] <cchildress> my setup is pretty generic
[15:39] <cchildress> i just checked through every running process...there is no vsftpd running
[15:39] <JanC> so you start it, and then there is no vsftpd in ps output?
[15:39] <cchildress> yeah
[15:40] <cchildress> it gives me a pid, but i immediately check taht pid and nothing is running
[15:40] <cchildress> it's like it's saying "ok i'm running here" but then silently failing or something
[15:42] <JanC> but did you check for a vsftpd with another PID like in that forum thread?
[15:42] <cchildress> yeah
[15:42] <cchildress> not a single instance of vsftpd is running
[15:42] <cchildress> even though the start command doesn't generate any errors
[15:45] <JanC> do you have a listen option in /etc/vsftpd.conf ?
[15:45] <cchildress> listen=yes
[15:45] <cchildress> local_enable=yes
[15:45] <cchildress> write_enable=yes
[15:50] <cchildress> strange little problems like this drive me nuts
[15:54] <JanC> cchildress: what happens when you run vsftpd from the command line?
[15:56] <cchildress> 500 OOPS: config file not owned by correct suer, or not a file
[15:56] <cchildress> i think we have a winner here...
[15:56] <cchildress> fwiw, /etc/vsftpd.conf is root:root
[15:57] <cchildress> /etc/init/vsftpd.conf is also root:root
[15:57] <JanC> sounds right
[15:57] <cchildress> so i don't know why it's complaining that the owner isn't right
[15:59] <cchildress> i think i found my problem
[15:59] <JanC> did you start vfstpd as root?
[15:59] <cchildress> yeah i found my problem
[15:59] <cchildress> vsftpd was failing to launch because "use_ssl" was enabled in /etc/vsftpd.conf
[15:59] <cchildress> yet there was no rsa cert
[16:00] <cchildress> so i commented out the line
[16:00] <cchildress> and now it runs fine
[16:00] <cchildress> for some reason, vsftpd never gave an error or even errored on the log, when run by upstart
[16:00] <cchildress> only by manually running it as root did i get the error about ssl
[16:00] <cchildress> so frustrating! lol at least it works now
[16:02] <cchildress> thank you very much for patiently helping me, JanC 
[16:03] <cchildress> btw, i'd like to report this as a "bug", since vsftpd gave no errors. would i report this bug to the upstart team, or vsftpd team?
[16:53] <SpamapS> cchildress: just vsftpd I think. upstart already has a feature planned to log the output of jobs, but for now the programs need to handle their own error logging.
[16:53] <SpamapS> cchildress: if vsftpd doesn't have a "check my configuration" option then I'm not sure we can do much.
[16:54] <cchildress> fair enough
[16:55] <cchildress> if upstart is already planning to log job output, then the "bug" will get fixed in time anyway
[16:55] <cchildress> so i'll just leave it be. thanks for the info
[16:58] <SpamapS> cchildress: its one of those things I'm really excited about for the future of upstart. :)
[16:58] <SpamapS> Because I'm silly like that
[16:58] <cchildress> yeah but that's an important feature!
[16:58] <SpamapS> state rewrite.. mmm.. ok.. but log my job output to a ring buffer.. SWEET
[16:58] <cchildress> for instance, if upstart had logged job output, i'd have known what teh problem was in the first few minutes...not after a half hour of head-scratching
[17:00] <cchildress> but anyway yes that sounds like a great feature