[00:08] How do I tell LP that it's a bug report about hardy? [00:11] owh - https://bugs.launchpad.net/ubuntu/hardy/+bugs [00:12] kgoetz: Yes, but how do I add my bug report, Bug #201237 to that list - do I just add a "hardy" tag? [00:13] owh: if you click 'report bug' it should reporta bug on hardy, aiui [00:14] kgoetz: Hmm, that seems to indicate that I need to delete the bug report I just made and do it again. That doesn't seem right. [00:14] owh: Let me look at the bug. [00:15] https://bugs.launchpad.net/ubuntu/+source/tasksel/+bug/201237 [00:15] ubotu seems asleep at the wheel again :) [00:16] Yeah [00:16] The only thing I see it nominate for a release. [00:16] Dunno if that's the right way though [00:16] owh: I'd suggest ask in #ubuntu-bugs [00:16] Cool, will do. [00:22] Launchpad bug 201237 in tasksel "tasksel does not work if installed on a machine with no network" [Undecided,New] https://launchpad.net/bugs/201237 [00:24] ROTFL [00:25] FYI the suggestion in #ubuntu-bugs was to indeed nominate it for hardy, then it may or may not actually be approved by the maintainer for such inclusion. [00:26] OK [00:59] I need some help. I'm still trying to track down why a cron.daily job isn't running. The script runs fine from a command-line. I'm wondering how I can "simulate" the cron environment so I can see what it's doing. There was a suggestion to install mail on this server to attempt to catch any output that might be generated, but I'm reluctant to do that on this production server. Any suggestions / comments / reading material? [01:00] I would second the email notify setup, you never know what else isn't working and is trying to notify you via mail [01:00] i'll third it - why wouldnt you want mail on a production sytem? [01:00] There will be some minimal logging to syslog. [01:01] the only other thing i can think of is redirect syslog to another system and bump up crons reporting [01:01] another option is to cat /etc/crontab, look for the daily line, and run that [01:01] You could also wrap your cronjob in something that logs to a logfile. [01:01] it might rotate all of your logs though :) [01:01] owh: What does the script do? [01:01] first thing i'd check with not-runnign cronjobs is crons $PATH [01:02] And, yes, I was going there. ;) [01:02] infinity: It backs up vmware images. [01:02] cron's PATH is, by default, rather lacking. [01:02] You should set PATH either in your cronjob, or the script being run by said cronjob. [01:03] That's a point that I had not considered. [01:03] Also, the mail side of things, under Debian I can setup local mail only, is that available under Feisty-server, I'm unsure. [01:03] Yup. [01:03] Both postfix and exim4 should give an option to be local-only. [01:04] Well, that simplifies things. [01:04] postfix might even default to it these days. Not sure, as I'm a disciple of Exim. [01:04] Ok, given the "overwhelming" suggestion to install mail, I might do that first. [01:05] (Exim-lover though I am, though, I'd recommend postfix from the "it's the Ubuntu default, and you're more likely to get IRC support for it" perspective) [01:05] Yeah, exim here too, but I'll go with the Ubuntu default. [01:05] i'm not familar with postfix's debconf, but exims is good for that sort of 'just need basic mail' stuff [01:05] If you know exim well enough, do Exim. We support both (ie: both are in main) [01:05] exim4-daemon-light, select "local only", profit. [01:05] i personally love ssmtp, its so much less of a headache to configure [01:05] Any particular reason you like exim btw? (/me doesn't know about either) [01:05] I'll do a quick test before I do it for real :) [01:05] don't know about any local only settings though [01:06] ssmtp has the distinct disadvantage of not delivering local mail. :) [01:06] Nice for getting mail OFF the host, though. [01:06] I'm expecting that tasksel will do the right thing. [01:06] Ok, thanks for knocking me into place, I'll investigate some more :) [01:06] infinity: which is really all you need in a server :) [01:06] anthony: I've been using exim for a decade, I know the spec inside out and backwards, and I've contributed hudreds, if not thousands, of lines of code to the project. [01:06] anthony: In other words, I'm terribly biased. [01:06] hehe [01:07] me on the other hand, have never contributed code to either :) I just know that 5-6 lines of conf files and i'm done :) [01:07] infinity: That's a pretty good reason. :) [01:08] infinity: You would have been a handy person to know some years ago when two instances of exim refused to send email between each other for some unfathomable reason. Network sniffing indicated that one instance would just give up. Never did find out why, but upgrading one side "fixed" it :) [01:08] bah, you love sendmail.cf, admit it [01:08] ROTFL [01:08] I think postfix likely wins in the "ease of use" category, but I still feel like I can do a lot more with exim's config files, when I want to do something "weird". [01:08] faulkes-: My introduction to sendmail.cf was on an Apple AU/X server :) [01:09] For those wondering, Apple made Unix before OS/X :) [01:09] faulkes-: sendmail is why I love exim, to be honest. Exim is nowhere near as confusing, but manages to be just as powerfully configurable. [01:09] s/Unix/Unix servers/ [01:09] owh: s/made/licensed/ [01:09] * faulkes- lalalalala m4 I can't hear you [01:09] infinity: Yeah, a bit of that too :) [01:09] heh, you had to love the bat book [01:10] owh: It's okay, your secret's safe with me. My first at-home UNIC box was an Amiga. [01:10] * faulkes- remembers doing some terribly awful things to sendmail.cf [01:10] (First UNIX machine I played with that I didn't own was OSF) [01:10] infinity: Now that's personal torture :) [01:10] * infinity misses DEC. [01:11] * kgoetz gives infinity an Alphaserver 5/300 [01:11] * owh misses the Alpha on the desktop and the VAX heard in the back office :) [01:11] *3000 [01:11] * kgoetz missed the whole era :@ [01:11] I have a DEC3k/900 lying around here. [01:11] * owh started with 3.5kb RAM on a 6502 based Vic20 :) [01:12] * kgoetz goes to sulk [01:12] Never got around to porting the turbchannel drivers from Linux/MIPS to Linux/Alpha, so the thing still boots NetBSD/Tru64. [01:12] infinity: It seems that you have waaaay too much time on your hands :) [01:14] If only that were true. [01:15] * owh misses a serial link between the Vic20 and the Apple ][ joystick port to transfer images from floppy to the Vic20 tape drive :) [01:15] If I had more spare time, the HPPA port would be in better shape, we'd have an Ubuntu/Alpha port "just cause", and I'd still be working on m68k glibc/kernel stuff. [01:15] infinity: This morning I was lamenting all the things I want to do, but just don't have enough hours in the day for, so I know what you're talking about. [01:16] infinity: are you just a serial porter? [01:17] kgoetz: Well, no. I work for Canonical on the buildd infrastructure. But, yeah, I used to do a lot of porting before this. [01:17] kgoetz: No time anymore, really. [01:17] The irony is that while I was lamenting that, I remembered a TV show last night about the Royal Family and the strange things that people get up to. While I might not get to do all that I want, at least what I'm doing is improving the community around me, so it made me feel a tad more useful than the accountant who plays police officer for Liz when she visits Scotland one week in the year. [01:18] infinity: So, think of all the good you're doing :) [01:19] How do I stop an installer from apt-getting stuff during installation? [01:19] remove the network cable [01:20] Hmm, yes, I suppose I can disable the interface in VMware. [01:20] Sigh, I thought there might be a more elegant way :) [01:20] log into the installer console and try to ifdown the nics? [01:21] That might work after it's configured them. [01:21] Excellent suggestion. [01:23] i'm a few minutes late, but you could also repoint its dns server to something bogus.... [01:24] Fair idea, bit of extra work beyond Alt-F2, Enter, ifconfig down eth0 [01:24] But valid :) [01:25] owh: or even shorter: ifdown eth0 (if the installer supports it) [01:25] kgoetz: Nope :) [01:26] aww [01:26] Tried that :) [01:26] :) [01:30] would i be correct in guessing these dirs are misnamed? http://archive.ubuntu.com/ubuntu/dists/hardy/main/installer-sparc/ [01:37] Can someone please explain why if I've just logged into a machine, either via a login prompt or by unlocking the screensaver, I still am required to enter the same password in sudo? I'm unsure why this might be considered "safer". I'm not saying, never prompt for a sudo password, having it expire in the same way as it does between sudo calls is fine, but why? [01:38] Anyone have opinions on ebox? [01:38] anthony: It will be the server gui of choice RSN. [01:40] owh: And does that translate to "it's decent" or "it's the best of server GUIs, but all server GUIs are terrible"? [01:40] :) [01:41] anthony: Personally, I'm leaning toward the latter, but that is based on looking at it, not using it. I don't feel that I'm a fair observer. [01:42] anthony: I'm sure that there are other opinions in this room. [01:42] owh: Fair enough. I _can_ handle cli configuration, but might give it a look anyway, since if it works that would be very convenient at times. [01:54] According to the debian manual aptitude can install tasks, but the man page doesn't divulge how that might be achieved. With apt-get, you can specify with a trailing caret (^), this doesn't work with aptitude. How do I do this? [01:55] * owh cannot use tasksel because it hangs at 100% due to a bug. [02:02] owh: what are you trying to install and how? [02:02] The task mail-server [02:02] :) [02:04] I wanted to just run tasksel, but the box is running Feisty and it stops at 100% - this is on my VM instance, not production. So, then the work-around is to install the task from the commandline: apt-get install mail-server^, but my preference is for using aptitude. [02:04] I'm not gaim to try this on the production server just yet :) [02:04] s/gaim/game/ :) [02:05] ok.. what happens when you do a 'apt-cache search mail-server' [02:05] I get procmail and gup back. [02:05] There are no packages with that name, the '^' in the apt-get command takes care of that. [02:06] i'm not sure what documentation is throwing an extra ^ in the line, but apt-get doesn't use them in any special way [02:06] No, the way to install a task with apt-get is to supply the task name with a '^' at the end. [02:07] if you are still looking to get tasksel installed, you can try 'apt-get install tasksel' -- or maybe i'm just lost and not helping much :) [02:07] No, tasksel is installed, but a bug in debconf stops it from working properly. There's a bug about it. [02:07] This is leaning towards, suck it up and use apt-get rather than aptitude :) [02:09] i've only used apt-get, ignorant and happy about it :) [02:09] ROTFL :) [02:09] I'm just going to emulate a different install and see what gives. [02:11] Well, well, well. aptitude install postfix worked just fine and dandy, no dovecot, and other stuff :) [02:14] mmmmmkay, glad you figured it out, i think i need to figure out if this screen is causing my headache or not :) [02:15] andguent: What is the refresh rate set to? [02:17] 60hz :) I usually can handle that fine.... its TFT too [02:17] owh: Tasks in apititude are something like ~t^taskname, I think. It's been a while. [02:17] owh: apt-get's interface works for me, and it's what I use on the buildds. [02:18] infinity: Tah, I ended up just installing postfix with no mail-server task :) [02:20] infinity: there's another interface besides apt-get ??? :-) [02:20] well, I mean other than dselect [02:20] lamont: Now that there is autoremove, not really :) [02:21] kirkland: ping [02:21] * lamont was introduced to the aptitude version of easter eggs the other day... most cute. [02:23] lamont: I suppose it beats the flight simulator in Excel :) [02:24] apt-get moo? [02:24] andguent: And others. [02:24] andguent: that's the apt-get version... aptitude has a similar one [02:26] somehow, that just doesn't surprise me [03:51] infinity: On the buildds, can you run "extra" scripts and get reports? [03:53] infinity: kirkland and I are trying to get init.d scripts to output a meaningful status. I've created some scripts to figure out what has an init.d, and I'm grepping those for "status)", but I wondered if the packages all get installed during build testing and if they are subjected to any standard tests. [03:54] infinity: Likely it isn't possible, but I just wondered. [04:00] owh: packages are checked by lintian/linda for validity, or do you mean something past that? [04:02] kgoetz: We're trying to determine first of all which packages have an init.d script, then which of those supports "status", then which of those is LSB compliant. Fix bugs/Add code accordingly. [04:02] I just wondered if the buildds would accommodate that, rather than installing each package and testing. [04:03] At present I have all the steps untill "installing the package" and running the init.d script with "status". [04:03] owh: you dont have to install - you could download the packages and dpkg -x them (i did lots of looking into those same sorts of questions) [04:03] brb though, say 5 min [04:03] kgoetz: Cool. [04:08] back [04:09] determining if something has an init script should be relatively easy. not sure about status (not sure what this means) or lsb compliance, because i dont know whats involved [04:09] kgoetz: Yes, I've written the scripts and have all that detail, now I need to determine what it might output. [04:09] kgoetz: https://wiki.ubuntu.com/OnnoBenschop/ubuntu-server/init.d-status [04:11] what is status? [04:11] is it an upstart thing? [04:11] kgoetz: It tells you if the package is running etc. [04:13] owh: any reason to `find -type f` instead of `find -name \*.deb`? [04:13] kgoetz: Yes, there are udebs in there too. [04:13] kgoetz: Besides the package dirs should only contain packages :) [04:14] they shouldnt contain spaces either :) (which i think are fair assumptions, fwiw) [04:16] :) [04:16] * owh wrote a nice big disclaimer at the top :) [04:16] * kgoetz saw, and was a bit confused by it [04:17] kgoetz: It really wasn't intended for anything other than initially getting a handle on the status. If we're going to do this for real, I suspect I'll have a little think about it. Mind you, dpkg -x should handle it, the spaces are simple enough. [04:17] faulkes-: Does your graphing magic handle IRC logs? [04:18] owh: quote the variables and it shouldnt be a problem [04:18] kgoetz: Yup. [04:19] kgoetz: I didn't because I got beat up by echo -e and trying to output a \t. [04:19] Why do we care about status in init scripts? [04:20] Well, when we finally get ebox to do its thing, it might be useful :) [04:20] I'm sure that there is a high-brow LSB answer too somewhere :) [04:21] s/high-brow/official/ [04:21] I'll try it a different way then ... [04:21] owh: What caused you to care enough to write the script? [04:21] Ah, there was some discussion about it. Lemmie have a gander in my logs. One mo. [04:23] * kgoetz thought upstart meant no init scripts [04:23] *init.d [04:23] ScottK2: Yesterday: (08:34:04) kirkland: owh: mathiaz and I were talking earlier today about getting more of the scripts in /etc/init.d LSB-compliant [04:24] ScottK2: So blame mathiaz and kirkland :) [04:25] Really, getting a status back is not a bad idea. You can then use that status in other places. If there is a standard way of doing it, makes life easier. [04:25] Does that answer the question, or did I just head off on a wild goose chase? [04:26] kirkland started volunteering and I had a few hours to put some scripts together. [04:32] Makes me wonder what the heck status is supposed to provide, but not so much I'm going to go hunt it down. [04:32] kirkland told me he had a link, I'll get him to dig it up for us for tomorrow's meeting :) [04:36] ScottK2: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html [04:39] Current version is 3.2.0, but the specs for this appear to be the same. [04:39] That makes sense I guess. [04:40] The nice thing about it is that you can then use the status in other places, a web gui, a cron job, etc. [04:53] kgoetz: Is it a reasonable assumption in my script that: a package with init.d script has it stored inside the /etc/init.d directory, not created by post installation script [04:54] owh: yes. as a rule [04:54] That is, if I unpack it with dpkg -x, I'll have an etc/init.d directory. [04:54] Cool [04:54] So far so good then :) [04:56] what i'm not sure of is if it will have a directory structure, or if you should grep the install scripts for a mv blah /etc/init.d [04:57] kgoetz: Well thus far I've had etc/init.d directories, but a grep for etc/init.d might be useful. [05:18] kgoetz: Lots of false positives, example scripts, help documents, procps (which has 'cp' in the name :), but nothing that indicates any other means of creating an init.d script. [05:18] s/Lots/Found lots/ [05:19] owh: what did you grep for? [05:19] grep -ra '/etc/init.d' ${temp_dir}/* | grep -E 'mv|cp' [05:20] The only one that jumped out at me in any way was python-twisted-core, but that appeared to be sample code only. [05:22] I suppose we could install *all* applications and see what falls out the bottom :) [05:22] * owh is kidding. [05:25] kgoetz: Hmm, I suppose for a package to be compliant it needs to register all its files. The ones installed are plain, but the ones we're looking for would perhaps be classed as config files. [05:27] owh: what do you mean by 'registered'? [05:28] In the dpkg list, there's a file for each package. I cannot recall what its called. [05:28] /var/lib/dpkg/info/*.list [05:30] That directory appears to be full of init.d references :) [05:31] yep. [05:31] have you thought about grabbing source packagefs instead of binary? [05:31] how do i write new blueprints? [05:31] kgoetz: Well, at present I'm just using the .iso [05:31] i don't find the option [05:31] owh: ah right [05:31] kgoetz: I figured I'd just start at one end :) [05:32] nxvl: https://blueprints.launchpad.net/ubuntu/ 'register a blueprint' [05:32] ? [05:32] owh: yep [05:32] kgoetz: thnx [05:33] The comments we're making here aren't going to waste, so keep poking me in the eye! (I'm adding them to a list to add to the wiki page.) [05:37] i'm stopping- i'm heading off :) [05:38] Thanks for your comments! [05:38] afk. heading home [05:38] no worries :) [05:42] kgoetz: thnx === cjwatson_ is now known as cjwatson [07:55] Morning! [08:00] <_ruben> mornin Jeeves_ .. having fun with your sun servers? ;) [08:03] _ruben: Not yet :) [08:03] Connected them with alom [08:04] But need to fix some stuff first [08:04] * Jeeves_ is having arguments with the Cisco they're connected to :) [08:05] <_ruben> hehe [08:05] <_ruben> looked at the pics the other day .. lookin sweet ;) [08:06] <_ruben> quite a shitload of disks ;) [08:07] Indeed :) [08:08] <_ruben> was kinda curious about the cooling though .. they look rather tightly stacked together [08:08] I just requested an seperate vlan and IP-space, so we should be able to play with them this afternoon [08:08] _ruben: What about it? [08:10] <_ruben> well .. there's not much room for airflow i think? [08:22] _ruben: There's a lot of heat coming from the rear. So the airflow manages to get there :) [08:41] hi , how can i list the runlevel processes?, please any help [08:44] 09:37 < bitrot> Config on router jun1.kelvin changed by user 'daniel' with comment add Ubuntu vlan [08:44] Noc is doing their thing ;) [08:47] <_ruben> heh .. irc feedback of noc operations? how sweet :) [08:47] morning [08:48] _ruben: snmptraps [08:50] <_ruben> Jeeves_: ah .. something ive been meaning to investigate as well .. am in the progress of replacing our crappy d-link switches with 3com ones at one of our hosting environments [08:50] <_ruben> there's only very little info to be found on the details of the various traps [08:51] _ruben: Replacing 'crappy' switches with 3com? [08:51] Those are crappy as well! :) [08:54] <_ruben> Jeeves_: cisco had my preference, but would've cost 2-3 times more .. and compared to the d-link ones, the 3com ones are rather spectacular .. and who knows, maybe they'll be replaced with cisco's eventually .. if these turn out to not be adequate either ;) === \sh_away is now known as \sh [10:13] jdstrand: stateless ipv6 autoconfiguration is something common used in an desktop environment. in any case its more common used than dhcpv6 [11:04] henkjan: I read up on it and committed it. it should hit sometime today [11:10] jdstrand: okay [11:10] thnx for quick fixing :) [11:15] np ;) [11:17] jdstrand: would you like to have access to an ipv6 enabled host for testing? [11:18] i can create a xen domU for testing purposes [11:18] * jdstrand ponders that [11:19] Hi, I would like to install a server version of Ubuntu on a tiny PC [11:19] The PC is built on VIA Eden running at 200MHz and booting from a CF card. [11:19] Any suggestion on where to find a good manual for this task? [11:41] morning [12:02] henkjan: I appreciate the offer, but I think at this time it is not required [12:03] henkjan: not a lot are using ipv6 right now, and I think we are ok. Perhaps we can revisit this in the future? [12:14] jdstrand: okay [12:22] hello everyone [12:23] got a question about rdac module [12:23] im currently using some DSxxxx hw with centos systems [12:23] what is current support for rdac in ubuntu? [12:33] http://ipv6.google.com/ [12:33] 13:03 < jdstrand> henkjan: not a lot are using ipv6 right now, and I think we are ok. Perhaps we can revisit this in the future? [12:34] jdstrand: Too bad you feel that way [12:34] Jeeves_: please explain. [12:34] ipv6 is fully supported in ufw [12:35] Jeeves_, hey mate [12:35] I just didn't want henkjan to have to go through all the administrative overhead of giving me access to one of his machines [12:35] when I can test ipv6 here locally [12:35] i wont be able to installfest tomorrow :( one of the test team decided he wanted to play with solaris [12:36] Jeeves_: ^^ [12:37] jdstrand: Cool that it's supported! Did I misinterpreted the 'not a lot are using ipv6 right now, and I think we are ok'? [12:37] Jeeves_: I think so [12:37] Jeeves_: I was responding to henkjan asking if I wanted access to an ipv6 enabled machine of his [12:38] I thought you made the often made chicken-egg mistake. My bad. [12:38] np [12:38] Kamping_Kaiser: I'm about to configure alom here and there [12:39] And I've got two of them :) [13:23] It pings! [13:23] Anyone knows the default T1000 ALOM pass? [14:25] Booting T1000 ... [14:26] noooooo... he'll go after John Conner! [14:27] <_ruben> haha [14:27] here all week [14:27] sommer? sounds a little close to conner [14:27] and as we all know, john does use computers [14:27] something you aren't telling us? [14:28] it's not me it's skynet... [14:28] * _ruben hides [14:33] Hmm [14:33] I don't have keyboard on the console [14:35] hasta la vista baby? [14:53] guys, there was some discussion about a Ubuntu Small Business Server edition, is that still somewhere or no? [14:56] shirish: ebox? :) [15:00] Jeeves_: dunno what ebox is [15:00] shirish: http://www.ebox-platform.com [15:00] * shirish thinks it might be something to do with server & enlightment wm [15:01] dexem: thanx, will check it out. [15:01] shirish: Webinterface for SBS-ish stuff [15:01] btw Ubuntu Server doesn't have its own homepage? Everything on the wiki only? [15:04] also does somebody have info. about the specific kernel which ships with the server image, any mail/link explaining the difference between the desktop kernel & server kernels would be great :) [15:07] found it, just sharing it with u guys as well, http://www.serverwatch.com/tutorials/article.php/3715071 seems pretty nice :) [15:22] mathiaz: for 3.0.28a debian dropped a bunch of patches so we dropped them as well [15:24] zul: cool ! [15:25] http://pastebin.ca/939747 [15:26] mathiaz: hey, https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/201287 [15:26] Launchpad bug 201287 in apache2 "apache2 init script support for 'status'" [Undecided,New] [15:27] kirkland: exzzellent... [15:27] mathiaz: so I'm working on cron now [15:28] kirkland: now could you also check if all the other bits required for lsb compliant scripts are available ? [15:28] mathiaz: apache was nice, in that it already had a built in "pidof" function and call and dependencies [15:28] mathiaz: cron does not [15:28] mathiaz: pidof is part of sysvutils [15:28] kirkland: I think that pidof is actually a function provided by the lsb init functions [15:29] mathiaz: well, the command line utility is in sysvutils [15:29] perhaps there's a function.... [15:29] mathiaz: so i didn't want to add sysvutils as a Depends [15:29] mathiaz: but I was thinking of adding it to Recommends [15:30] and making `etc/init.d cron status` fail gracefully if pidof not found [15:30] mathiaz: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html [15:30] that's what's required by lsb [15:31] mathiaz: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptfunc.html [15:31] lsb also requires a pidofproc function [15:31] kirkland: there is a pidofproc function [15:31] k [15:31] kirkland: available in /lib/lsb/init-functions [15:31] let me try that [15:32] mathiaz: LSB has some tests [15:36] mathiaz: pidofproc works like a charm! [15:36] * kirkland high fives mathiaz [15:54] zpool1 8.4T 39K 8.4T 1% /zpool1 [15:54] Hmmm [15:56] kirkland: "pidofproc"? [15:56] soren: http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptfunc.html [15:56] soren: /lib/lsb/init-functions [15:57] kirkland: That's a rather unfortunate description.. "Only process identifiers of running processes should be returned" [15:58] soren: unfortunate why? [15:58] kirkland: So only if they're in actual running state in which case it'd be a no-op on a non-smp system. [15:58] or.. [15:58] on processes which are in the process table, which is redundant since that's the only way they could have a pid. [15:59] s/^on/only/ [16:00] yay: https://bugs.edge.launchpad.net/ubuntu/+source/samba/+bug/201442 [16:00] Launchpad bug 201442 in samba "ffe for samba 3.0.28 to 3.0.28a" [Undecided,New] [16:00] soren: seems okay for me for daemons, which is the target here [16:01] soren: are you quabling with the wording of the spec, or the actual use of the function? [16:01] * kirkland still can't tell when soren is joking ;-) [16:02] kirkland: The wording of the spec. === soren is now known as soren_not_joking [16:02] soren_not_joking: thanks, that will keep things clear... just keep /nick up to date at all times :-) === soren_not_joking is now known as soren_joking [16:02] I will. === soren_joking is now known as soren [16:03] <_ruben> Jeeves_: that could hold a lot of pr0n^H^H^Hrepository files [16:03] :P [16:03] soren: right, so running processes means to me processes in the process table [16:03] soren: which may or may not be active/sleeping [16:04] Right. Which other kinds of processes have pid's? [16:04] None. [16:04] So it's redundant (and thus confusing) [16:04] soren: ps -ef | grep defunct [16:04] Specifications should be exact and to the point. [16:04] <_ruben> Jeeves_: what kind of raid setup is that btw? [16:05] _ruben: No clue. [16:05] Trying to rebuild the whole stuff using zfs [16:05] kirkland: So all /runnable/ processes? [16:05] <_ruben> Jeeves_: hehe [16:06] I'm new to ZFS [16:06] <_ruben> Jeeves_: but i do hope there's hardware raid involved? :) [16:06] kirkland: "runable", perhaps. [16:06] * soren is not sure [16:06] _ruben: zfs is software-raid, AFAIK [16:06] _ruben: But it's built for being a fileserver [16:07] kirkland: Where do I send patches for that spec? :) [16:07] soren: i know a couple of the IBM guys who work on it [16:07] let me check [16:09] soren: it's Linux Foundation, now, so perhaps in a month in Austin [16:09] <_ruben> Jeeves_: seems zfs has raid0/raid1 and 'custom versions' of raid5 and raid6 .. looks nice on first sight [16:09] kirkland: I'll print out 500 copies of a patch and distribute it all over the place and see what happens :) [16:10] :-) [16:11] okay, so the apache2 package doesn't have a -1ubuntu in its name [16:11] which means that it's just a straight up debian package? [16:11] Yup. [16:11] kirkland: yes [16:12] * mathiaz thinks about all the trees in Denmark [16:12] mathiaz: looking at the changelog, i don't even see a -1ubuntu version in its history... does that mean ubuntu patching it is unprecedented (and therefore highly unlikely)? [16:12] kirkland: it was - just that when a package is synced, the changelog is dropped [16:13] kirkland: otherwise we'd have to keep a merge [16:13] mathiaz: i see.... [16:13] mathiaz: how, then, do I get around this error: "dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address [16:13] " [16:14] kirkland: did you set the Maintainer field to core-dev ? [16:14] mathiaz: did you see the blueprint i started yesterdays [16:14] mathiaz: i subscribed yourself to it [16:14] mathiaz: nope, I suppose that has to be done, since we've modified the package, then [16:16] nxvl: I've noticed - still have to read thourgh your proposal [16:16] nxvl: did you look at the previous specs and the pages in wiki.ubuntu.com about previous attempts ? [16:17] * zul thinks about all the bacon in denmark [16:17] kirkland: yes - https://wiki.ubuntu.com/DebianMaintainerField [16:17] mathiaz: i based the wiki page on ufw one [16:17] nxvl: I meant about the content [16:17] mathiaz: i'm not still finished with the spects, but the base idea is already descriebed [16:17] nxvl: there are a couple of spec written up for simplifing the administration of an ubuntu server [16:18] mathiaz: yes, i take a look at some of them [16:18] mathiaz: but nothing so similar as i want to [16:19] mathiaz: also, the tool i want can be used in the future for complete desktop and/or serve administrator, as it is modular [16:33] Who is my date for tomorrow morning, for playing with the T1000's ? === leonel_ is now known as leonel [16:38] henkjan: Says it is pschulz01 [16:39] are you right or left handed? [16:41] mathiaz: see http://launchpadlibrarian.net/12607821/apache2_init_status.diff [16:42] mathiaz: that look better? [16:44] kirkland: yes - what about the comment on pidof apache2 in pidof_apache2 ? [16:44] kirkland: # if pidof is null for some reasons the script exits automagically [16:44] kirkland: # classified as good/unknown feature [16:44] mathiaz: :-) yeah, funny, huh? i did hit that bug [16:44] mathiaz: and I found that putting the || true inside the shell call fixed it for me [16:44] mathiaz: hence my comment [16:45] * kirkland notes that those comments were unchanged by kirkland [16:45] kirkland: yes - but the apache maintainer added a "# classified as good/unknown feature" [16:46] kirkland: if you've fixed a good feature, it ain't no good ;) [16:46] mathiaz: i took that as a poor attempt at comedy [16:46] mathiaz: calling a "bug" a "feature" [16:46] kirkland: under which condition did you hit the bug ? [16:46] mathiaz: in the case where there are no apache2's running [16:46]