/srv/irclogs.ubuntu.com/2007/03/10/#upstart.txt

=== khermans__ [i=administ@nat/cisco/x-361219dbbc0b826a] has joined #upstart
=== theCore [n=alex@ubuntu/member/theCore] has joined #upstart
=== Md [i=md@freenode/staff/md] has joined #upstart
=== Md [i=md@freenode/staff/md] has joined #upstart
=== administrator_ [i=administ@nat/cisco/x-fedbc0ca9b370c8d] has joined #upstart
=== j_ack [n=rudi@p508D95BA.dip0.t-ipconnect.de] has joined #upstart
=== int0x0c [n=ben@161.253.47.94] has joined #upstart
=== int0x0c [n=ben@161.253.47.94] has joined #upstart
=== int0x0c [n=ben@161.253.47.94] has joined #upstart
=== Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart
=== administrator_ [i=administ@nat/cisco/x-607c23dd90cafeb8] has joined #upstart
=== mbiebl [n=michael@dialin-145-254-249-245.pools.arcor-ip.net] has joined #upstart
=== phsdv [n=paul@dyn-88-122-33-87.ppp.tiscali.fr] has joined #upstart
=== pkt [n=pantelis@85.75.171.157] has joined #upstart
=== pkt [n=pantelis@athedsl-285854.otenet.gr] has joined #upstart
=== Md [i=md@freenode/staff/md] has joined #upstart
=== Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart
=== _ion [i=johan@kiviniemi.name] has joined #upstart
=== j_ack [n=rudi@p508DB43F.dip0.t-ipconnect.de] has joined #upstart
=== phsdv [n=paul@dyn-88-122-33-87.ppp.tiscali.fr] has joined #upstart
=== administrator_ [i=administ@nat/cisco/x-1a796513494e6b04] has joined #upstart
=== Keybuk [n=scott@wing-commander.netsplit.com] has joined #upstart
Keybuk*bounce*09:09
AlexExtremehey09:09
AlexExtremei'll test out 0.3.7 tomorrow hopefully09:09
Keybukcool09:09
KeybukI've not had any death threats yet, so it seems to be working09:09
AlexExtremeheh09:09
Keybukalready thinking what to put in the next version09:13
Keybukthink the big change will have to be re-implementing restart09:13
_ionkeybuk: The resources idea sounds great.09:39
Keybukdifficult it is deciding which state it needs to stay in09:39
Keybukstart/waiting I gues09:39
_ionkeybuk: It would be nice if a shell script could make the 'uses' information.09:40
_ionE.g. block-device-added could find out the actual physical device for any of /dev/sda1, /dev/mdsomething and /dev/lvm-volumegroup/something, and say 'uses $DISKNAME' based on that.09:41
_ions/block-device-added/the fsck job/09:42
Keybukwhy would the disk size make a difference?09:43
_ionSize?09:43
Keybukoh09:43
Keybukdunno where I read that09:43
=== Keybuk blames the wine
_ion:-)09:43
Keybukyeah, the problem there is you'd have to either include that in the event, or compute it in the jobs09:45
KeybukI'm inclined to suggest the event is better there though, since it probably *has* that information in the first place09:46
Keybukand it's cheaper than calculating it on every single job09:47
_ionGood point.09:47
Keybukit's just DEVICE=$(readlink /sys$DEVPATH/device) after all09:47
_ionFor LVM and MD, /sys/block/$foo/slaves seems to be the right way to find the physical device.09:52
Keybukyeah, it'd be annoying to code all the different logic into the "check the filesystem" event09:53
Keybukuh job09:53
KeybukAND any other job that wants it09:53
_ionTrue.09:53
Keybukmuch easier to handle it in the specific events09:53
Mdbe sure to check a > 2.6.20 kernel with the compat sysfs links disabled :-)09:53
_ionOh, 'slaves' is deprecated?09:53
Keybukno, device is going away09:54
_ionAh09:54
Keybukbecause /sys/block/hda itself is a symlink09:54
Keybuklike I said, much easier to put this into the event emission09:54
KeybukMd: that hasn't happened yet though?09:55
Mdwhat?09:55
Keybukthe move of block devices to under the physical device09:56
Keybuk(which means the device symlink is still necessary)09:56
MdI am not sure, I had to roll back because the 2.6.21rcsomething rawhide kernel broke resume from RAM on my system (any clue about how to debug this? the screen is not working, but I can reboot using magic sysrq)09:57
Keybuk2.6.20 here, /block/hda is still a directory09:57
Keybukthat may be caused by the deprecated option though, looking at the code09:58
Keybukmight have to try turning it off and see what happens09:58
AlexExtremewait09:59
AlexExtremeumm09:59
AlexExtremewrong channel09:59
AlexExtremesorry09:59
cortanadumb question, perhaps, but how stable are the contents of /sys?10:15
Mdnot much so far10:16
Keybukabout as stable as upstart's job definition syntax :p10:17
=== phsdv [n=paul@dyn-88-122-33-87.ppp.tiscali.fr] has joined #upstart
_ionExcuse my ignorance, but what's the correct way to find the corresponding /sys/block/... path for a file in /dev, e.g. sda*, md*, mapper/*? Comparing the contents of /sys/block/**/dev to the device types of the /dev files probably works, but there's a better way, isn't there?10:26
Md_ion: udevinfo -n I think10:27
Keybukudevinfo -q path -n hda110:28
Keybukthough you're not *really* supposed to use udevinfo as a database <g>10:28
_ionThanks. Works for sda1 and md0, but not /dev/mapper/*.10:29
Keybukdid you try dm-0 as the name?10:29
Md_ion: because these are not managed by udev10:29
Keybukudevinfo -q path -n dm-010:29
KeybukMd: they are in Ubuntu10:29
_ion"no record for 'dm-0' in database" (an Edgy box)10:30
Keybukhmm10:32
Keybukdunno how to make a devmapper device10:32
Keybukdmsetup create foo just blocks10:32
Keybukah10:33
=== Keybuk pressed ^D
Keybukwing-commander scott# udevinfo -q path -n mapper/foo10:33
Keybuk/block/dm-010:33
_ionFunny, doesn't work here.10:39
Keybukhmm10:48
Keybukfeisty?10:48
=== j_ack [n=rudi@p508DB43F.dip0.t-ipconnect.de] has joined #upstart

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!