[01:54] anyone know why I have to put my seed file in the initrd for it to work? === Justin_ is now known as W8JKC === Justin_ is now known as W8JKC === Justin_ is now known as W8JKC === freaky[t] is now known as fReAkY[t] [05:36] How do I grep for a /? grep -E / -F and any combination of \/home/sites\\\/ doesn't seem to work. [05:36] I'm trying to find the string "/home/sites/" [05:36] \/ [05:37] \/home\/sites I think will work. [05:39] Just put it in quotes. [05:40] ScottK: `grep -rHn "\/home\/sites\/" *` doesn't work as expected, it produces all sorts of spurious results which don't appear to contain home or site [05:41] hads: You mean juse use `grep -rHn "/home/sites/" *` ? That also produces spurious results for me [05:41] What hads said should work. [05:41] whats wrong with ls [05:43] Yeah, `grep "/home/sites/" *` should be fine. [05:46] Ok, so it does work, the error was elsewhere, sorry [05:46] I was running `grep -rHn "/home/sites/" * | less` [05:47] Then in less, /home didn't return any results, but the text was there, less just didn't find it properly [05:47] chmac: what are you tring to acomplish [05:51] jameswf-home: I've moved a site from one server to another, the old path was /home/sites/ the new one is different [05:51] I wanted to find all instances of /home/sites/ in the new htdir [05:52] I was piping it to less because it was returning a line from an SQL cache file which was extremely long, so it was cluttering my screen [05:52] I thought that grep wasn't working because when I tried searching in less, for "home", it wasn't found, so I thought grep was returning nonsense [05:53] Turns out that less wasn't finding the text home, probably because it was too far along the line or something [05:53] As in, the line was too long [06:04] If there's something you don't want in your results just pipe a grep -v on the end [06:09] maybe perl or sed would be better suited [06:09] grep ia a bit of a brut [06:18] hello - how can I install libcurlftpfs on the old Ubuntu dapper ? [06:19] i cannot compile it from source - too many errors [06:19] jameswf-home: grep is brut? grep is fantastic. [06:19] hads for globs and rough searches yes for specifics not so much [06:20] Then there's egrep :) [06:22] for i in `find /path/to/dir/` do sed -n '/\/home\/sites\//p'; done [06:23] doj [06:23] for i in `find /path/to/dir/` do sed -n '/\/home\/sites\//p' $i; done [06:23] Umm, ok. [06:26] Thanks for all the grep help guys, got it sorted now and the site is running well :) [06:26] Now to buy some furniture... [06:55] hello can I pls get some help installed libcurl3-dev ? so many dependencies.... [07:24] how how do you pipe in ftp commands after ftp host command? [07:59] nc [08:33] moin [08:49] Howdy.. anyone sucessfully pushing 'search-domains' to clients using DHCP? [08:59] im stuck on this apache vhost issue [09:01] osmosis: "this apache vhost issue"? [09:07] soren: Im setting a ServerName for my VirtualHost, but its still using the default config rather then the new config I am specifying. [09:11] here is the config I am using, http://dpaste.com/75192/ [09:12] the second virtual host is not working. I dont know why. [09:12] The first one doesn't list a servername? [09:12] Is that intentional? [09:13] And please elaborate on "is not working". [09:29] Anyone use procmail ? [09:31] pschulz01: Yes. [09:31] Are you using any rules on the "Delivered-To:"? [09:31] header? [09:32] soren: I'm trying to use the procmail to keep a globol archive of incoming email... [09:33] pschulz01: No, no rules on Delivered-To [09:33] soren: .. but .. it looks as though some email doesn't get a 'Delivered-To:' header (or the match doesn't work) which causes procmail to barf and bounce the message back through postfix. [09:34] Er... What? [09:34] If a procmail rule doesn't match, it just falls through and lands in the default mailbox. [09:34] Ok.. (email)->Postfix->Procmail [09:35] Procmail fails with "procmail: Exceeded LINEBUF".. which is a a little stupid, as I've made the LINEBUF huge (32k). [09:35] How have you configured postfix to pass things to procmail? [09:35] .. and the log indicates that procmail: No match on "^Delivered-To: \/[^@]+" [09:36] What do your delivered-to headers look like? [09:38] soren: Default ubuntu-server install (I believe).. but.. (looking) [09:38] soren: Ahha! in main.cf [09:38] main.cf:mailbox_command = /usr/bin/procmail [09:41] i have an Ubuntu 7.10 postfix and procmail box with dovecot for imapd and pop3, what files do i need to move to my new 8.04 server to migrate this setup? [09:51] bbl [09:52] pschulz: Ok. Yeah, that looks just right. Do you have an example e-mail that fails like that? (with the "Exceeded LINEBUF" thing) [10:08] Is there any chance someone could have a look at the NIS package? === ogra_ is now known as ogra [10:57] broonie, what sort of look? [10:58] Bambi_BOFH: The major thing would be to disable Network Manager support by default (since it causes no end of bug reports) [10:59] Bambi_BOFH: But there's also some long-standing issues with the ordering of NIS in the init process which appear to be getting no love at all. [11:00] not sure where to follow that up. -dev, i guess, but you could try -motu or -bugs [11:01] It's in main so motu isn't appropriate. [11:01] -devel suggested I try here for someone who might want to look at it. [11:02] hm. [11:02] * broonie is the Debian manintainer; I could provide patches but my experience hasn't been all that positive. [11:03] nod [11:03] * Bambi_BOFH wont be the one to step forward, not a lot of time atm :( [11:25] * NCommander is away: This creature sleeps beyond the reaches of time itself [11:25] hello, how can I use ls command to show subdirectories [11:41] ghaleb__: -R is recursive, it will show all subdirs and contents recursively [11:43] thefish: thank you, I want it to tape data using cpio [11:44] ghaleb__: you want to back up just the listing? [11:46] no [11:46] ls | cpio -oVc > /dev/rmt/0 [11:46] ls -R would backup subdirectories as well === ogra_ is now known as ogra [12:52] hi all [12:53] i have one problem with ubuntu server installation [12:53] how can i get root pwd ? [12:53] !root [12:53] Do not try to guess the root password, that is impossible. Instead, realise the truth... there is no root password. Then you will see that it is 'sudo' that grants you access and not the root password. Look at https://help.ubuntu.com/community/RootSudo [12:56] when I installing it dont ask to type root pwd. [12:57] no, it wouldnt have [12:57] look at the wiki page meantioned [12:57] ok thanks [15:02] I think something went wrong during the install when it was configuring apt, where can I find out what sources.list is supposed to contain in ubuntu-server 7.10 ? [15:13] * delcoyote hi [15:23] broonie: I remember some talk between you and someone else a while back... Was it Michael Vogt perhaps? [15:28] Not me. [15:29] I did ask about this on -devel a couple of days ago. I also spoke via msg with someone who was patching a FTBFS but they didn't seem terribly confident in doing anything substantial. [15:32] Oh, I probably spoke to mvo about n-m causing constant problems. [15:33] broonie: Yeah, that sounds about right. [15:33] broonie: What are the nature of your problems, exactly? In Ubuntu Server we don't have network-manager by default. [15:34] As far as network manager goes it appears that a reasonable number of people enable NIS on their clients then have n-m break it. [15:35] So it'd be nice if someone would disable n-m support by default for release at least. [15:36] That'd stop the overwhelming majority of bug reports about NIS in Ubuntu. [15:37] I don't think it's desparately related to server itself either but -devel bounced me here for someone who might care (which I suppose makes some sense since servers tend to have clients). [15:39] woho! [15:40] dell reseler in croatia now offers ubuntu :) [15:50] broonie: Disable n-m- for release? I don't think I follow? [15:50] broonie: You want us to have the development releases have n-m enabled, but then disable it at release time (kind of like apport)? [15:50] soren: Or just disable it all the time, I don't care either way. [15:51] (the n-m integration in NIS, this is) [15:52] broonie: I'm not sure what n-m integration NIS does? [15:52] ypbind can use n-m to detect when there is a worknig network connection. [15:52] I've not used NIS in a non-server environment, so no network-manager. [15:52] broonie: Ok. Sounds reasonable enough? [15:52] Unfortunately on some systems n-m constantly lies about this. [15:53] ivoks: Neat! Maybe Denmark will follow soon! [15:53] soren: heh, laptop for 300euros :) [15:54] otherwise they are starting at 500€ here [15:55] broonie: Ok.. I realise this is a problem for NIS, but it doesn't sound like anything you can solve from the NIS side. [15:55] broonie: Let's try it this way: What do you propose as an alternative? [15:58] ypbind can be told to ignore n-m by default [15:58] Which sidesteps the issue. [15:59] But in case n-m isn't lying and there's actually no network available, I don't suppose that's handled particularly gracefully? [15:59] This is what Debian shipped for etch and will ship for lenny. [16:00] It handles it as gracefully as it ever did which isn't too bad - there's a long timeout at startup but other than that it works. [16:00] broonie: I suppose there's a bug open about this? [16:01] I strongly expect a very small proprotion of users actually make use of NIS in configurations where this is a likely occurrence and their system is still usable without it. [16:01] There's ones like #224828 [16:02] bug 224828 [16:02] Launchpad bug 224828 in nis "NIS demon fails during startup if the roaming mode is turned off" [Undecided,New] https://launchpad.net/bugs/224828 [16:05] broonie: From the looks of that bug, it seems that nis only checks for network during startup. Is that accurate? [16:06] broonie: I would have expected it to spring to life when the network connection came around. [16:06] soren: no, that's not the case at all. [16:06] Well, not so much "checks for network", but "checks whether HAL thinks we have network". [16:06] broonie: Ok. [16:07] It checks whenever n-m claims the status changes. [16:07] Ok. [16:07] * soren rereads [16:09] broonie: Ok, so the problem is that n-m says "connected" too soon, so nis checks and finds that there's actually no network, and since n-m's state never changes, nis doesn't recheck? [16:09] If that's not it either, can you please explain it again? [16:09] When n-m goes to connected state it may not be connected. [16:10] The n-m status may change again but since it would be leaving the connected state nis will beleive that the network has been disconnected === emgent is now known as emgent`NL [16:11] So when connected is reported it is too soon and since it only generates events on status changes there's no kick to re-check. [16:11] NIS should be coping better with this but disabling the network manager integration is a simple, non-invasive workaround. [16:12] broonie: Have you talked to network-manager people about this? [16:12] soren: They don't appear to care. [16:12] broonie: No response at all? [16:12] Basically, yes. [16:13] AFAICT NIS is only marginally supported in Ubuntu anyway. [16:14] broonie: Have you checked n-m 0.7's behaviour? [16:15] broonie: I just checked, and nm-tool doesn't seem to say "connected" until I'm actually connected. [16:15] It's always worked on a lot of systems. [16:15] ... [16:15] Appears to be related to the NIC driver. [16:15] Or possibly the local network. [16:16] I wonder... Why does nis go and recheck whether the network is there, if n-m says it's there? [16:16] It doesn't. [16:17] What it does is try to use the IP address of the interface which falls over because none has been assigned. [16:17] Ok, is there a bug that actually has all this information in it, so that I don't have to sit here and guess all the right questions to ask? [16:18] Probably not a single one. [16:18] They mostly get assigned over to n-m and then triaged/closed away. [16:19] Example? [16:19] Also, have you checked it with n-m 0.7? [16:19] Sorry, I don't archive the relevant info. [16:19] No, I've never been able to reproduce this on my own systems. [16:20] You said something in the beginning about patches.. [16:21] Someone (not me) patched a FTBFS in nis in ubuntu recently. [16:21] They spoke to me about it for some reason. [16:22] 10:02:43 * broonie is the Debian manintainer; I could provide patches but my experience hasn't been all that positive. [16:25] Oh, that. Essentially that's a case of figuring out how to put a patch into lp and get it applied; most of the problems are process/lp usage ones. [16:28] So you have patches? Or not? [16:29] It's a one line patch, I can generate it trivally when I get home. [16:29] Or now, for that matter. [16:30] does it just pass --no-dbus to nis? [16:30] Or does it fix network-manager? [16:30] The former. [16:30] It's really not very appealing. Asking network-manager about the status of the network seems like a reasonable thing to do. [16:31] I agree; ideally there would be a better fix. [16:35] I would very much like to know if the problem persists in Intrepid (i.e. with n-m 0.7) [17:05] soren: AFAICT the best thing for that is to wait for release and see if anyone complains. [17:06] nis users tend not to be early adopters :/ [17:12] I dont know any admin/friend who uses nis, instead all they use ldap/nss [18:16] broonie: perhaps there is some way to disable nm integration at runtime rather than compile time? [18:26] siretart: That's what I'm suggesting people enable. [18:27] siretart: There's a default configuration file in the package, I'm suggesting changing that default to disable the n-m integration. [18:32] an ubuntu directory server is a great idea === fReAkY[t] is now known as freaky[t] [20:29] how can i make a sort of symlink to /home/torrentflux/acemo in a proftpd folder so that the symlinked folder is actually accessable through ftp? === PrivateVoid is now known as PV_Away [22:14] broonie: that sounds reasonable to me. do you happen to know if there is already a bug about this that I could reference in the changelog? === freaky[t] is now known as fReAkY[t] === fReAkY[t] is now known as freaky[t] [23:56] Morning.. [23:56] soren: ping? [23:57] I'm still having procmail issues, which I'd like to get to the bottom of.. [23:58] but.. I would rather write up the problem I am having somewhere as a 'blueprint' or 'answer' as I'm sure that there is a better way of doing what I am trying to do.