IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 15 August 2008   (all times are UTC)

00:02ball has quit IRC
00:02ball has quit IRC
00:18btil has quit IRC
00:18btil has quit IRC
00:35johnny has left #ltsp
00:35johnny has left #ltsp
00:41johnny has joined #ltsp
00:41johnny has joined #ltsp
00:54MacIver has quit IRC
00:54MacIver has quit IRC
00:55MacIver has joined #ltsp
00:55MacIver has joined #ltsp
00:58Nubae has quit IRC
00:58Nubae has quit IRC
01:01Nubae has joined #ltsp
01:01Nubae has joined #ltsp
01:10plamengr has joined #ltsp
01:10plamengr has joined #ltsp
02:45Nubae has quit IRC
02:45Nubae has quit IRC
02:58japerry has quit IRC
02:58japerry has quit IRC
03:48The_Code has joined #ltsp
03:48The_Code has joined #ltsp
03:56Nubae has joined #ltsp
03:56Nubae has joined #ltsp
04:01alekibango has joined #ltsp
04:01alekibango has joined #ltsp
04:07Nuba1 has joined #ltsp
04:07Nuba1 has joined #ltsp
04:08bobby_C has joined #ltsp
04:08bobby_C has joined #ltsp
04:33Nubae has quit IRC
04:33Nubae has quit IRC
05:18Nuba1 has quit IRC
05:18Nuba1 has quit IRC
05:24yallax_on has joined #ltsp
05:24yallax_on has joined #ltsp
05:29
<yallax_on>
i have xubuntu ltsp installed, and added the users to the "fuse" group, when they insert a usb-disk it gets mounted in /media/"username"/usbdisk-sdb1 it seems.. but there is no icon on the desktop or anything.. if i logon locally on the server it works tho.. but how to i fix it so users gets the icon on their desktop??
05:29
i have xubuntu ltsp installed, and added the users to the "fuse" group, when they insert a usb-disk it gets mounted in /media/"username"/usbdisk-sdb1 it seems.. but there is no icon on the desktop or anything.. if i logon locally on the server it works tho.. but how to i fix it so users gets the icon on their desktop??
05:33ogra has quit IRC
05:33ogra has quit IRC
05:33ogra has joined #ltsp
05:33ogra has joined #ltsp
05:46etyack has joined #ltsp
05:46etyack has joined #ltsp
06:07jim`` has quit IRC
06:07jim`` has quit IRC
06:09jim`` has joined #ltsp
06:09jim`` has joined #ltsp
06:18yallax_on has quit IRC
06:18yallax_on has quit IRC
06:21J45p3r___ has joined #ltsp
06:21J45p3r___ has joined #ltsp
06:24Q-FUNK has joined #ltsp
06:24Q-FUNK has joined #ltsp
06:40Nick_Hill has joined #ltsp
06:40Nick_Hill has joined #ltsp
06:42mikkel has joined #ltsp
06:42mikkel has joined #ltsp
06:42
<Nick_Hill>
I have been away from LTSP fr a year or two, and noticed several changes based on the Ubuntu install. Eg using SSH instead of XDMCP. Are there any block diagrams or flow charts to show how the different programs interact? I am trying to work out why I can't log into a new user account until I have re-booted the server.
06:42
I have been away from LTSP fr a year or two, and noticed several changes based on the Ubuntu install. Eg using SSH instead of XDMCP. Are there any block diagrams or flow charts to show how the different programs interact? I am trying to work out why I can't log into a new user account until I have re-booted the server.
06:44
I am also finding the laptop used as a (temporary) thin client hangs for 3 or 4 minutes on boot-up, and don't know how to start debugging the new LTSP.
06:44
I am also finding the laptop used as a (temporary) thin client hangs for 3 or 4 minutes on boot-up, and don't know how to start debugging the new LTSP.
06:44
<cyberorg>
Nick_Hill, http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/ltsp-theory.html
06:44
Nick_Hill, http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/ltsp-theory.html
06:45
<Nick_Hill>
Thanks.
06:45
Thanks.
06:45
<cyberorg>
http://en.opensuse.org/How_Does_KIWI-LTSP_work
06:45
http://en.opensuse.org/How_Does_KIWI-LTSP_work
06:45
most parts are similar to ubuntu's
06:45
most parts are similar to ubuntu's
06:47
<Nick_Hill>
I get the impression that Ubuntu LTSP compresses the entire LTSP chroot and delivers it over TFTP. So no NBD or NFS.
06:47
I get the impression that Ubuntu LTSP compresses the entire LTSP chroot and delivers it over TFTP. So no NBD or NFS.
06:51
<laga>
that's wrong
06:51
that's wrong
06:51
the squashfs is exported over nbd
06:51
the squashfs is exported over nbd
06:53yallax_on has joined #ltsp
06:53yallax_on has joined #ltsp
06:56
<Nick_Hill>
laga, I see. NBD being a network block device.
06:56
laga, I see. NBD being a network block device.
06:57J45p3r___ has left #ltsp
06:57J45p3r___ has left #ltsp
07:01Blinny has joined #ltsp
07:01Blinny has joined #ltsp
07:09hersonls has joined #ltsp
07:09hersonls has joined #ltsp
07:10hersonls has joined #ltsp
07:10hersonls has joined #ltsp
07:13
<Nick_Hill>
If I create a user account on the server, I can't log into that user account through the thin client until I rebooted the server. Is this normal?
07:13
If I create a user account on the server, I can't log into that user account through the thin client until I rebooted the server. Is this normal?
07:15
I don't get username/password failed. Screen goes blank then log-in screen comes back.
07:15
I don't get username/password failed. Screen goes blank then log-in screen comes back.
07:19
<etyack>
Nick_Hill: try ltsp-update-sshkeys on the server.
07:19
Nick_Hill: try ltsp-update-sshkeys on the server.
07:30
<Nick_Hill>
etyack, ltsp-update-sshkeys makes no difference. I suppose SSH is involved with authentication, and I can log into the account through SSH. Perhaps some other service is involved with logging int he thin client. Re-booting the server works even where the thin client isn't rebooted.
07:30
etyack, ltsp-update-sshkeys makes no difference. I suppose SSH is involved with authentication, and I can log into the account through SSH. Perhaps some other service is involved with logging int he thin client. Re-booting the server works even where the thin client isn't rebooted.
07:30plamengr has quit IRC
07:30plamengr has quit IRC
07:34
<etyack>
Nick_Hill: have you tried ltsp-update-image?
07:34
Nick_Hill: have you tried ltsp-update-image?
07:35
<ogra>
thas rather a prob with the user, not related to ltp at all ...
07:35
thas rather a prob with the user, not related to ltp at all ...
07:35
check /var/log/auth.log and the users ~/.xsession-errors
07:35
check /var/log/auth.log and the users ~/.xsession-errors
07:35
*ltsp
07:35
*ltsp
07:35
<etyack>
it's odd rebooting the server fixes the problem. are you able to log in locally on the server with the new account?
07:35
it's odd rebooting the server fixes the problem. are you able to log in locally on the server with the new account?
07:36
<Nick_Hill>
I can log in locally on the new account.
07:36
I can log in locally on the new account.
07:36
<ogra>
please check the above two files *while* logging in with a brandnew account ...
07:37
please check the above two files *while* logging in with a brandnew account ...
07:37
also what do you use to create the account ?
07:37
also what do you use to create the account ?
07:37
(gui ? a script ? adduser on the commandline ? )
07:37
(gui ? a script ? adduser on the commandline ? )
07:38
<Nick_Hill>
I have the same effect, whether using the Gnome GUI or adduser
07:38
I have the same effect, whether using the Gnome GUI or adduser
07:38
<ogra>
so what do the logs expose for a user you have never logged in with before ?
07:38
so what do the logs expose for a user you have never logged in with before ?
07:39
<Nick_Hill>
/var/log/auth.log accepted password for account5 ... session opened for user account 5
07:39
/var/log/auth.log accepted password for account5 ... session opened for user account 5
07:39
<ogra>
that looks ok
07:39
that looks ok
07:40
so your problem is the gnome-session not staring correctly by whatever reason
07:40
so your problem is the gnome-session not staring correctly by whatever reason
07:40
check the ~/.xsession-errors file
07:40
check the ~/.xsession-errors file
07:41
<Nick_Hill>
Nothing written to ~/.xsession-errors
07:41
Nothing written to ~/.xsession-errors
07:41
<ogra>
so your session doesnt even start ... weird
07:41
so your session doesnt even start ... weird
07:41
did you tweak anything from the defaults on that ubuntu ?
07:41
did you tweak anything from the defaults on that ubuntu ?
07:41
<Nick_Hill>
The set-up is pristine.
07:41
The set-up is pristine.
07:42
<ogra>
does the homedir exist after you created a user ?
07:42
does the homedir exist after you created a user ?
07:42
and is it owned by that user ?
07:42
and is it owned by that user ?
07:42
which ubuntu version is that ? hardy (8.04.1) ?
07:42
which ubuntu version is that ? hardy (8.04.1) ?
07:42
<Nick_Hill>
installed ubuntu 8.04 from CD, updated packages, aptitude install ltsp-server-standalone, ltsp-build-client, ltsp-update-sshkeys, ltsp-update-image
07:42
installed ubuntu 8.04 from CD, updated packages, aptitude install ltsp-server-standalone, ltsp-build-client, ltsp-update-sshkeys, ltsp-update-image
07:43
8.04.1
07:43
8.04.1
07:43
Home directory exists after creating user.
07:43
Home directory exists after creating user.
07:43
<ogra>
hmm, should just work (it does for everyne else)
07:43
hmm, should just work (it does for everyne else)
07:43
<Nick_Hill>
I can log into the account locally.
07:43
I can log into the account locally.
07:43
<ogra>
ldap involved or something ?
07:43
ldap involved or something ?
07:43
<Nick_Hill>
Not unless default set-up. All defaults selected.
07:43
Not unless default set-up. All defaults selected.
07:44
So basically, start server, start client. Create account. Log in locally all OK, Try to log in through client. NOK. Reboot client. No change. Reboot server. Can log in.
07:44
So basically, start server, start client. Create account. Log in locally all OK, Try to log in through client. NOK. Reboot client. No change. Reboot server. Can log in.
07:46bobby_C has quit IRC
07:46bobby_C has quit IRC
07:48* ogra hasnt seen anything like that ever
07:48* ogra hasnt seen anything like that ever
07:49
<Nick_Hill>
I have a friend who runs a cybercafe. He'll be able to test his 8.04.1 soon.
07:49
I have a friend who runs a cybercafe. He'll be able to test his 8.04.1 soon.
07:50mccann has joined #ltsp
07:50mccann has joined #ltsp
07:52
<Nick_Hill>
I have tried re-starting SSH, I have tried re-starting GDM. No change. I suspect there is a program caching authentication data somewhere, OR a script running at boot-up changes something.
07:52
I have tried re-starting SSH, I have tried re-starting GDM. No change. I suspect there is a program caching authentication data somewhere, OR a script running at boot-up changes something.
07:53
<ogra>
there is no such thing ...
07:53
there is no such thing ...
07:53
the only server side part involved in the login process is actually ssh ...
07:53
the only server side part involved in the login process is actually ssh ...
07:53
<Nick_Hill>
Just tried init 1 then init 2. Made no difference.
07:53
Just tried init 1 then init 2. Made no difference.
07:53
<ogra>
gdm isnt used
07:53
gdm isnt used
07:54
<Nick_Hill>
I know.. it is weird. I am trying it for the third time.
07:54
I know.. it is weird. I am trying it for the third time.
07:57
Tried again. Same. I'll try init 1, then re-start any other process I can find.
07:57
Tried again. Same. I'll try init 1, then re-start any other process I can find.
08:07hersonls has quit IRC
08:07hersonls has quit IRC
08:08
<Nick_Hill>
ogra, I know you'll think I am making some really fundamental mistake, but I am just reporting what I find: ring server to run level 1. Nothing except for a couple of instances of bash for the current screen. Bring server back to run level 2. Can't log in. Re-boot server. Can log in. I'll try again dirtying memory locations.
08:08
ogra, I know you'll think I am making some really fundamental mistake, but I am just reporting what I find: ring server to run level 1. Nothing except for a couple of instances of bash for the current screen. Bring server back to run level 2. Can't log in. Re-boot server. Can log in. I'll try again dirtying memory locations.
08:08ball has joined #ltsp
08:08ball has joined #ltsp
08:09
<ogra>
i dont think you make any mistake.... but i'm honestly out of ideas and have never ever seen such behavior
08:09
i dont think you make any mistake.... but i'm honestly out of ideas and have never ever seen such behavior
08:11
and there isnt any service that would affect users in a way that they couldnt log in after initial creation but could log in after reboot
08:11
and there isnt any service that would affect users in a way that they couldnt log in after initial creation but could log in after reboot
08:11
so poking around in runlevels is unlikely to help
08:11
so poking around in runlevels is unlikely to help
08:11
your ssh connection seems to work fine according to auth.log
08:11
your ssh connection seems to work fine according to auth.log
08:12
so there can only be somethig wonky with the desktop session or the homedir
08:12
so there can only be somethig wonky with the desktop session or the homedir
08:13
is your home on a separate partition ?
08:13
is your home on a separate partition ?
08:15
<Nick_Hill>
home dir is exactly as default, on root partition. I can log into the new account immediately locally.
08:15
home dir is exactly as default, on root partition. I can log into the new account immediately locally.
08:17
I thought that there just might be a problem with a program accessing a previously initialised /un-initialised memory location. So tried dd if=/dev/hda of=/dev/null, after killing all non-kernel processes, to re-write memory locations. No change
08:17
I thought that there just might be a problem with a program accessing a previously initialised /un-initialised memory location. So tried dd if=/dev/hda of=/dev/null, after killing all non-kernel processes, to re-write memory locations. No change
08:17
s/hda/sda
08:17
s/hda/sda
08:18
The only other conclusion I can come to is that some kernel service is caching auth info.
08:18
The only other conclusion I can come to is that some kernel service is caching auth info.
08:18ogra has quit IRC
08:18ogra has quit IRC
08:22gate_keeper_ has joined #ltsp
08:22gate_keeper_ has joined #ltsp
08:25bobby_C has joined #ltsp
08:25bobby_C has joined #ltsp
08:26ogra has joined #ltsp
08:26ogra has joined #ltsp
08:30Gadi has joined #ltsp
08:30Gadi has joined #ltsp
08:34mhterres has joined #ltsp
08:34mhterres has joined #ltsp
08:40Subhodip has joined #ltsp
08:40Subhodip has joined #ltsp
09:05Subhodip has quit IRC
09:05Subhodip has quit IRC
09:07elisboa has joined #ltsp
09:07elisboa has joined #ltsp
09:12jammcq has joined #ltsp
09:12jammcq has joined #ltsp
09:12
<jammcq>
g'morning friends
09:12
g'morning friends
09:14
<ball>
jammcq: mornin'
09:14
jammcq: mornin'
09:15plamengr has joined #ltsp
09:15plamengr has joined #ltsp
09:16otavio has quit IRC
09:16otavio has quit IRC
09:35otavio has joined #ltsp
09:35otavio has joined #ltsp
09:38Egyptian[Home] has quit IRC
09:38Egyptian[Home] has quit IRC
09:47_UsUrPeR_ has joined #ltsp
09:47_UsUrPeR_ has joined #ltsp
09:54
<etyack>
hey jammcq
09:54
hey jammcq
09:56
<mistik1>
hey jammcq etyack
09:56
hey jammcq etyack
09:56
ltns
09:56
ltns
09:56
<etyack>
hey mistik1
09:56
hey mistik1
09:57gate_keeper_ has quit IRC
09:57gate_keeper_ has quit IRC
10:09K_O-Gnom has joined #ltsp
10:09K_O-Gnom has joined #ltsp
10:10warren has quit IRC
10:10warren has quit IRC
10:11etyack has quit IRC
10:11etyack has quit IRC
10:21
<_UsUrPeR_>
Hey all. I'm working with a customer right now who is running Windows for DHCP with the following settings: http://www.wwnet.net/Untitled-1.jpg
10:21
Hey all. I'm working with a customer right now who is running Windows for DHCP with the following settings: http://www.wwnet.net/Untitled-1.jpg
10:22
It is getting various errors based on what is set in the "Root Path"
10:22
It is getting various errors based on what is set in the "Root Path"
10:22alekibango has quit IRC
10:22alekibango has quit IRC
10:22alekibango has joined #ltsp
10:22alekibango has joined #ltsp
10:23
<_UsUrPeR_>
with the root path list it is in the screen shot, it gives the error "No such file or directory. nfsmount error mounting 172.16.16.19:/opt/ltsp/i386. Illegal seek.
10:23
with the root path list it is in the screen shot, it gives the error "No such file or directory. nfsmount error mounting 172.16.16.19:/opt/ltsp/i386. Illegal seek.
10:23
If we remove the IP address, it gives the same error as above
10:23
If we remove the IP address, it gives the same error as above
10:24
if we remove the directory, it gives the error "No such file or directory"
10:24
if we remove the directory, it gives the error "No such file or directory"
10:24
if we remove the option in it's entirety, it gives the error "Could not find root path DHCP option"
10:24
if we remove the option in it's entirety, it gives the error "Could not find root path DHCP option"
10:24
and if we include the root option, but leave the field blank, it says "missing mount point"
10:24
and if we include the root option, but leave the field blank, it says "missing mount point"
10:25
how do I make this windows DHCP server happy? :(
10:25
how do I make this windows DHCP server happy? :(
10:28irule has quit IRC
10:28irule has quit IRC
10:29
<_UsUrPeR_>
anyone?
10:29
anyone?
10:29
<ball>
Is it mandatory for you to use Windows as the DHCP server?
10:29
Is it mandatory for you to use Windows as the DHCP server?
10:30
<Gadi>
_UsUrPeR_: what distro?
10:30
_UsUrPeR_: what distro?
10:30
(for LTSP)
10:30
(for LTSP)
10:30
;)
10:30
;)
10:32
<_UsUrPeR_>
oh, sotty
10:32
oh, sotty
10:32
Fedora 9
10:32
Fedora 9
10:32
sotty = sorry
10:32
sotty = sorry
10:32
<ball>
If I ever own a mungrel, I'll call him "sotty"
10:32
If I ever own a mungrel, I'll call him "sotty"
10:32
<_UsUrPeR_>
ball: yes. the customer has an all-windows network :|
10:32
ball: yes. the customer has an all-windows network :|
10:33
ball: good call. it's only one letter off
10:33
ball: good call. it's only one letter off
10:33
<Gadi>
fedora uses nfs?
10:33
fedora uses nfs?
10:33
<_UsUrPeR_>
gadi: I was confused as to why that was appearing at all to be honest.
10:33
gadi: I was confused as to why that was appearing at all to be honest.
10:33
gadi: because it doesn't
10:33
gadi: because it doesn't
10:34epoxy|w3rk has quit IRC
10:34epoxy|w3rk has quit IRC
10:35
<Gadi>
I don't know how fedora's initramfs looks
10:35
I don't know how fedora's initramfs looks
10:35
so, I don't know what options they have
10:35
so, I don't know what options they have
10:35
<ball>
_UsUrPeR_: the Xterminals are on the same physical LAN as Windows workstations? Ah, perhaps you're using the Windows workstations /as/ Xterminals?
10:35
_UsUrPeR_: the Xterminals are on the same physical LAN as Windows workstations? Ah, perhaps you're using the Windows workstations /as/ Xterminals?
10:35
<Gadi>
in Ubuntu, you would need to specify the nbd server and port in the pxelinux.cfg/default
10:35
in Ubuntu, you would need to specify the nbd server and port in the pxelinux.cfg/default
10:36
(as long as dhcp server != LTSP server)
10:36
(as long as dhcp server != LTSP server)
10:36
I do not know if fedora has made such an accommodation
10:36
I do not know if fedora has made such an accommodation
10:36
either way, you shouldn't need root-path at all
10:36
either way, you shouldn't need root-path at all
10:37
unless fedora uses it as a key for nbd
10:37
unless fedora uses it as a key for nbd
10:37
if warren's around, ask him
10:37
if warren's around, ask him
10:37
<_UsUrPeR_>
there is a pxelinux.cfg/default file
10:37
there is a pxelinux.cfg/default file
10:38
it looks like this:
10:38
it looks like this:
10:38
prompt 0
10:38
prompt 0
10:38
label linux
10:38
label linux
10:39
kernel vmlinuz.ltsp
10:39
kernel vmlinuz.ltsp
10:39
append rw initrd=initrd.ltsp quiet selinux=0 rhgb
10:39
append rw initrd=initrd.ltsp quiet selinux=0 rhgb
10:39
<Gadi>
try adding to the end of the append line:
10:39
try adding to the end of the append line:
10:39
<_UsUrPeR_>
where would I put the != LTSP server portion in there
10:39
where would I put the != LTSP server portion in there
10:39
<Gadi>
nbdroot=<ip:port>
10:39
nbdroot=<ip:port>
10:39
where port = 2000
10:39
where port = 2000
10:40
so: nbdroot=172.16.16.19:2000
10:40
so: nbdroot=172.16.16.19:2000
10:40
<_UsUrPeR_>
roger
10:40
roger
10:41
should I keep the root path in the DHCP config in Windows?
10:41
should I keep the root path in the DHCP config in Windows?
10:41
<Gadi>
you should not need it
10:41
you should not need it
10:41
but, what do I know?
10:41
but, what do I know?
10:41
I just work here
10:41
I just work here
10:41
<_UsUrPeR_>
:)
10:41
:)
10:41
guy's not around anyway
10:41
guy's not around anyway
10:42
thanks for the help. I'll give that a shot.
10:42
thanks for the help. I'll give that a shot.
10:42
I really wish using Windows DHCP was not required, but here we are :|
10:42
I really wish using Windows DHCP was not required, but here we are :|
10:43
<Gadi>
if there are a small number of clients, I believe Windows has dhcp exceptions
10:43
if there are a small number of clients, I believe Windows has dhcp exceptions
10:43
in other words, you can tell it by MAC addy who not to respond to
10:43
in other words, you can tell it by MAC addy who not to respond to
10:43
<_UsUrPeR_>
that is what they are doing right now
10:43
that is what they are doing right now
10:43
they are assigning static IP addresses based on mac
10:43
they are assigning static IP addresses based on mac
10:45
<Gadi>
so, if you tell it to ignore requests from the thin clients, you can re-enable dhcp on the ltsp server
10:45
so, if you tell it to ignore requests from the thin clients, you can re-enable dhcp on the ltsp server
10:45
and have it respond only to those clients
10:45
and have it respond only to those clients
10:45
of course, this is more management
10:45
of course, this is more management
10:45
but, a workable solution nontheless
10:45
but, a workable solution nontheless
10:45
*nonetheless
10:45
*nonetheless
10:49
<_UsUrPeR_>
ok. Just tested this out. It gave the same error as previous when the root path was removed
10:49
ok. Just tested this out. It gave the same error as previous when the root path was removed
10:49
and for SNG I re-added the root path, and it gave the "no seek error" again
10:49
and for SNG I re-added the root path, and it gave the "no seek error" again
10:54
is there a way to see if the client is requesting stuff from ndb?
10:54
is there a way to see if the client is requesting stuff from ndb?
10:56
<Gadi>
well, it would do that from the initramfs
10:56
well, it would do that from the initramfs
10:56
so, you would see a client negotiation happen
10:56
so, you would see a client negotiation happen
10:56
but, it sounds like you don't even get the kernel?
10:56
but, it sounds like you don't even get the kernel?
10:56warren has joined #ltsp
10:56warren has joined #ltsp
10:56
<warren>
_UsUrPeR_: ping
10:56
_UsUrPeR_: ping
10:57
_UsUrPeR_: try the ltsp-5.1.19 that I pushed to my repo
10:57
_UsUrPeR_: try the ltsp-5.1.19 that I pushed to my repo
10:57
_UsUrPeR_: build the chroot from scratch again
10:57
_UsUrPeR_: build the chroot from scratch again
10:57
<_UsUrPeR_>
warren: will do.
10:57
warren: will do.
10:57
warren: give me a bit though. I have another.... thing.... :/
10:57
warren: give me a bit though. I have another.... thing.... :/
10:57
<warren>
_UsUrPeR_: I got a Etherboot-5.0.5 client to work out of the box
10:57
_UsUrPeR_: I got a Etherboot-5.0.5 client to work out of the box
10:57
<Gadi>
warren: does you initrd allow for DHCP server != LTSP server?
10:57
warren: does you initrd allow for DHCP server != LTSP server?
10:58
<warren>
Gadi: if the DHCP server gives out a root-path it'll handle it.
10:58
Gadi: if the DHCP server gives out a root-path it'll handle it.
10:58
<Gadi>
you key off of root-path for nbd?
10:58
you key off of root-path for nbd?
10:59
_UsUrPeR_: is getting an "Illegal seek" error
10:59
_UsUrPeR_: is getting an "Illegal seek" error
10:59
when he tries
10:59
when he tries
10:59
<_UsUrPeR_>
oh, yeah. warren: look above. tell me if you see anything weird in there. This is a headache
10:59
oh, yeah. warren: look above. tell me if you see anything weird in there. This is a headache
11:01
<warren>
Gadi: not doing nbd at all
11:01
Gadi: not doing nbd at all
11:01
in the version pushed to the public
11:01
in the version pushed to the public
11:01
_UsUrPeR_: I only now joined the channel, I don't have info.
11:01
_UsUrPeR_: I only now joined the channel, I don't have info.
11:02
<_UsUrPeR_>
d'oh
11:02
d'oh
11:02
<Gadi>
warren: ah
11:02
warren: ah
11:02
nfs?
11:02
nfs?
11:02
<warren>
yes, nfs
11:02
yes, nfs
11:02
<_UsUrPeR_>
pm
11:02
pm
11:02
<Gadi>
_UsUrPeR_: your nfs server config is borked
11:02
_UsUrPeR_: your nfs server config is borked
11:02
:)
11:02
:)
11:02
try restarting nfs
11:02
try restarting nfs
11:02
<_UsUrPeR_>
wauugh
11:02
wauugh
11:02
<Gadi>
and/or the LTSP box
11:02
and/or the LTSP box
11:02
<warren>
_UsUrPeR_: did you try "service nfs restart"
11:02
_UsUrPeR_: did you try "service nfs restart"
11:03
oh. lunch time. brb
11:03
oh. lunch time. brb
11:05
<_UsUrPeR_>
huh
11:05
huh
11:05
looks like you may be correct. NFS mountd, daemon, quotas and services "failed" on restart
11:05
looks like you may be correct. NFS mountd, daemon, quotas and services "failed" on restart
11:05
then the second time around they were ok
11:05
then the second time around they were ok
11:06
testing this out now
11:05
testing this out now
11:06
awesome. that was it
11:06
awesome. that was it
11:06* _UsUrPeR_ buys a round of drinks for the channel
11:06* _UsUrPeR_ buys a round of drinks for the channel
11:12japerry has joined #ltsp
11:12japerry has joined #ltsp
11:15gbolte has joined #ltsp
11:15gbolte has joined #ltsp
11:19vagrantc has joined #ltsp
11:19vagrantc has joined #ltsp
11:36
<warren>
_UsUrPeR_: the ltsp-5.1.9 in my repo works?
11:36
_UsUrPeR_: the ltsp-5.1.9 in my repo works?
11:37
_UsUrPeR_: it creates a wraplinux-nbi image and automatically configures dhcpd to serve it.
11:37
_UsUrPeR_: it creates a wraplinux-nbi image and automatically configures dhcpd to serve it.
11:41ball has left #ltsp
11:41ball has left #ltsp
11:47
<vagrantc>
warren: with your tests of mknbi, did you make the combined kernel+initrd ?
11:47
warren: with your tests of mknbi, did you make the combined kernel+initrd ?
11:47
<warren>
vagrantc: yes.
11:47
vagrantc: yes.
11:47
<vagrantc>
ah, ok.
11:47
ah, ok.
11:47
<warren>
vagrantc: wraplinux --nbi seems to work on me for several clients
11:47
vagrantc: wraplinux --nbi seems to work on me for several clients
11:47
only thing I didn't test was BOOTP since that is incredibly ancient
11:47
only thing I didn't test was BOOTP since that is incredibly ancient
11:48
<vagrantc>
i've tested the mkelf-linux images and the mknbi-linux images fairly recently, and they worked on debian.
11:48
i've tested the mkelf-linux images and the mknbi-linux images fairly recently, and they worked on debian.
11:49Lns has joined #ltsp
11:49Lns has joined #ltsp
11:52
<warren>
wraplinux is actively maintained and hpa instantly fixes whatever I ask for
11:52
wraplinux is actively maintained and hpa instantly fixes whatever I ask for
11:52
and it seems to work on everything except coreboot
11:52
and it seems to work on everything except coreboot
11:52ninkendo has quit IRC
11:52ninkendo has quit IRC
11:52
<warren>
so i'm using wraplinux for everything, and mkelfimage for coreboot
11:52
so i'm using wraplinux for everything, and mkelfimage for coreboot
11:53johnny has left #ltsp
11:53johnny has left #ltsp
11:53ninkendo has joined #ltsp
11:53ninkendo has joined #ltsp
12:02johnny has joined #ltsp
12:02johnny has joined #ltsp
12:05jpdrawneek has joined #ltsp
12:05jpdrawneek has joined #ltsp
12:05
<jpdrawneek>
needs some help with a cisco switch - its not liking ltsp
12:05
needs some help with a cisco switch - its not liking ltsp
12:07
<gbolte>
how do you know its the switch?
12:07
how do you know its the switch?
12:07
<jpdrawneek>
Anybody awake?
12:07
Anybody awake?
12:07
replaced it with a 100mb hub and everything works
12:07
replaced it with a 100mb hub and everything works
12:08
<jammcq>
what's not working?
12:08
what's not working?
12:08Lns has quit IRC
12:08Lns has quit IRC
12:08
<warren>
jammcq: btw, you have the channel password?
12:08
jammcq: btw, you have the channel password?
12:08
<jpdrawneek>
pxe boot works
12:08
pxe boot works
12:08
its the next boot part after that
12:08
its the next boot part after that
12:08
<jammcq>
ummm, yeah, I think so
12:08
ummm, yeah, I think so
12:09
jpdrawneek: what version of ltsp?
12:09
jpdrawneek: what version of ltsp?
12:09
<jpdrawneek>
latest
12:09
latest
12:09
<jammcq>
what distro?
12:09
what distro?
12:09
<jpdrawneek>
suse
12:09
suse
12:09
<jammcq>
that's kiwi-ltsp, you prolly will need some help from them. But... try turning off 'Spanning Tree' in the switch
12:09
that's kiwi-ltsp, you prolly will need some help from them. But... try turning off 'Spanning Tree' in the switch
12:10
<jpdrawneek>
not nothing wrong with kiwi-ltsp - its the cisco thats doing it
12:10
not nothing wrong with kiwi-ltsp - its the cisco thats doing it
12:10
<warren>
jammcq: time to add Fedora to the list above
12:10
jammcq: time to add Fedora to the list above
12:10
<jammcq>
warren, yeah, good point
12:10
warren, yeah, good point
12:11ChanServ sets mode: +o jammcq
12:11ChanServ sets mode: +o jammcq
12:11
<gbolte>
hmm interesting
12:11
hmm interesting
12:12
jpdrawneek, is it a layer 3 switch?
12:12
jpdrawneek, is it a layer 3 switch?
12:12
if it is you need to make sure its not doing anything funky with broadcast messages
12:12
if it is you need to make sure its not doing anything funky with broadcast messages
12:14jammcq changes topic to "LTSP-5 is the current version that you should be using. Check out Ubuntu, Debian, Fedora and Opensuse for awesome integration"
12:14jammcq changes topic to "LTSP-5 is the current version that you should be using. Check out Ubuntu, Debian, Fedora and Opensuse for awesome integration"
12:14
<gbolte>
:)
12:14
:)
12:15
<jammcq>
is that better?
12:15
is that better?
12:15
and soon, hopefully we can put gentoo there
12:15
and soon, hopefully we can put gentoo there
12:16
<warren>
I don't know if I would call Opensuse was awesome integration.
12:16
I don't know if I would call Opensuse was awesome integration.
12:16
opensuse if you want something like LTSP
12:16
opensuse if you want something like LTSP
12:17
<jpdrawneek>
it seems pretty good
12:17
it seems pretty good
12:17
<ogra>
its totally non upstream
12:17
its totally non upstream
12:17
<jpdrawneek>
when you don't have an evil switch
12:17
when you don't have an evil switch
12:17* ogra agrees with warren "something like ltsp"
12:17* ogra agrees with warren "something like ltsp"
12:18
<ogra>
it assembles the functionallity going its own way
12:18
it assembles the functionallity going its own way
12:19jammcq changes topic to "LTSP-5 is the current version that you should be using. Check out Ubuntu, Debian and Fedora for awesome integration. Gentoo is getting very close and Opensuse has kiwi-ltsp."
12:19jammcq changes topic to "LTSP-5 is the current version that you should be using. Check out Ubuntu, Debian and Fedora for awesome integration. Gentoo is getting very close and Opensuse has kiwi-ltsp."
12:20
<ogra>
yeah, that sounds good
12:20
yeah, that sounds good
12:20
<warren>
yeah, that's good.
12:20
yeah, that's good.
12:20
<jammcq>
I figure that pays the proper respect to the people who are at least making some attempt
12:20
I figure that pays the proper respect to the people who are at least making some attempt
12:21
and, it gives the 'Awesome' to the distros with REAL ltsp support currently shipping
12:21
and, it gives the 'Awesome' to the distros with REAL ltsp support currently shipping
12:21etyack has joined #ltsp
12:21etyack has joined #ltsp
12:21
<ogra>
right and doesnt leave out the forks ... its not that kiwi-ltsp is bad ... just not upstream
12:21
right and doesnt leave out the forks ... its not that kiwi-ltsp is bad ... just not upstream
12:21
<jammcq>
yeah
12:21
yeah
12:22
<ogra>
anyway ...
12:22
anyway ...
12:22* ogra goes to make dinner
12:22* ogra goes to make dinner
12:22
<dberkholz>
johnny: yeah, i'll set aside some time this weekend to pull your stuff in and give it a last look over
12:22
johnny: yeah, i'll set aside some time this weekend to pull your stuff in and give it a last look over
12:22
<ogra>
cooking instead of smoking :P
12:22
cooking instead of smoking :P
12:23
<jammcq>
dberkholz: I'm happy to change that topic as soon as you say it's ready
12:23
dberkholz: I'm happy to change that topic as soon as you say it's ready
12:23
<laga>
ogra: good idea. :)
12:23
ogra: good idea. :)
12:24johnny has left #ltsp
12:24johnny has left #ltsp
12:25
<jpdrawneek>
gbolte: layer 2 I think
12:25
gbolte: layer 2 I think
12:27
<gbolte>
hmm
12:27
hmm
12:27
it must be doing some sort of filtering
12:27
it must be doing some sort of filtering
12:27johnny has joined #ltsp
12:27johnny has joined #ltsp
12:30
<dberkholz>
jammcq: we'll let ya know. =)
12:30
jammcq: we'll let ya know. =)
12:31
<jammcq>
cool
12:31
cool
12:31
ok guys, I gotta run. Going to visit my daughter at Penn State. she's starting grad school down there
12:31
ok guys, I gotta run. Going to visit my daughter at Penn State. she's starting grad school down there
12:32
<gbolte>
cool
12:32
cool
12:33jammcq has quit IRC
12:33jammcq has quit IRC
12:36
<ogra>
laga, well, i wont give up smoking completely ... but i reduced from 40-60 i smoked before down to max 5 that i allow myself ... (i havent hit the 5 in any of the last three days though, my max was three yet)
12:36
laga, well, i wont give up smoking completely ... but i reduced from 40-60 i smoked before down to max 5 that i allow myself ... (i havent hit the 5 in any of the last three days though, my max was three yet)
12:37
<laga>
ogra: i used to smoke 20-40 a day. quitting was the best thing i've ever done
12:37
ogra: i used to smoke 20-40 a day. quitting was the best thing i've ever done
12:37
<gbolte>
hmm so when are you going to switch from max 5 to max 3
12:37
hmm so when are you going to switch from max 5 to max 3
12:37
:P
12:37
:P
12:38bobby_C has quit IRC
12:38bobby_C has quit IRC
12:38
<ogra>
i wont switch to max 3 :) if i smoke less thats fine ... if i every lose interest and stop completely thas fine as well
12:38
i wont switch to max 3 :) if i smoke less thats fine ... if i every lose interest and stop completely thas fine as well
12:38
if i start again thats ok too but will need compensation ....
12:38
if i start again thats ok too but will need compensation ....
12:39
since i miss the time for to much compensation thats unlikely though :)
12:39
since i miss the time for to much compensation thats unlikely though :)
12:39
<warren>
more drinking?
12:39
more drinking?
12:40
<ogra>
well, i dont know what cause me to get into hospital (neither do the docs) so i try to reduce everything to a rather moderate level ... even drinking
12:40
well, i dont know what cause me to get into hospital (neither do the docs) so i try to reduce everything to a rather moderate level ... even drinking
12:40
;)
12:40
;)
12:40
*caused
12:40
*caused
12:41
anyway, back to the kitchen :)
12:41
anyway, back to the kitchen :)
12:44
<jpdrawneek>
jammcq: tree-span to fastport sorted it
12:44
jammcq: tree-span to fastport sorted it
12:46
<gbolte>
jpdrawneek, glad you have your setup working
12:46
jpdrawneek, glad you have your setup working
12:46
:D
12:46
:D
12:47
jpdrawneek, for future reference #opensuse-kiwi is the channel for kiwi specific problems
12:47
jpdrawneek, for future reference #opensuse-kiwi is the channel for kiwi specific problems
12:47
:)
12:47
:)
12:50Lns has joined #ltsp
12:50Lns has joined #ltsp
12:53
<jpdrawneek>
gbolte: its not a kiwi problem
12:53
gbolte: its not a kiwi problem
12:53
I could not get ubuntu ltsp to work either
12:53
I could not get ubuntu ltsp to work either
12:55
<Blinny>
beer?
12:55
beer?
12:56
<jpdrawneek>
Blinny: your round then....
12:56
Blinny: your round then....
12:57leio has joined #ltsp
12:57leio has joined #ltsp
13:02jpdrawneek has left #ltsp
13:02jpdrawneek has left #ltsp
13:16yallax_up has joined #ltsp
13:16yallax_up has joined #ltsp
13:17
<_UsUrPeR_>
ok
13:17
ok
13:18
warren: just got finished with a lot of crap. I feel accomplished! :D
13:18
warren: just got finished with a lot of crap. I feel accomplished! :D
13:18
warren: yesterday, I stopped after getting some wireshark reads from the server
13:18
warren: yesterday, I stopped after getting some wireshark reads from the server
13:18
warren: I was not able to see anything pertaining to what it was requesting in wireshark. Where should I be looking?
13:18
warren: I was not able to see anything pertaining to what it was requesting in wireshark. Where should I be looking?
13:19
<yallax_up>
my ltsp users have their home folder in /home/domain/username but all users seems to have read permissions on all their files for everyone.. id like to have permission 0700.. how can i do that automaticly, when a user logs in or his home folder is created?
13:19
my ltsp users have their home folder in /home/domain/username but all users seems to have read permissions on all their files for everyone.. id like to have permission 0700.. how can i do that automaticly, when a user logs in or his home folder is created?
13:24
or.. how do i make it so every new user has 0700 permission as default on their home folder
13:24
or.. how do i make it so every new user has 0700 permission as default on their home folder
13:25
<warren>
_UsUrPeR_: you have to go into detail view of the initial DHCP packet from the client
13:25
_UsUrPeR_: you have to go into detail view of the initial DHCP packet from the client
13:25
_UsUrPeR_: it has a client identifier string somewhere in there
13:25
_UsUrPeR_: it has a client identifier string somewhere in there
13:26
_UsUrPeR_: my Etherboot-5.0.5 client says "Etherboot-5.0" for example
13:26
_UsUrPeR_: my Etherboot-5.0.5 client says "Etherboot-5.0" for example
13:26
<_UsUrPeR_>
ok.
13:26
ok.
13:28bytor4232 has joined #ltsp
13:28bytor4232 has joined #ltsp
13:28
<bytor4232>
i would suggest trying your luck in the #ltsp channel.
13:28
i would suggest trying your luck in the #ltsp channel.
13:28
Or the #samba channel. If its active directory, its probably a samba issue.
13:28
Or the #samba channel. If its active directory, its probably a samba issue.
13:29bytor4232 has left #ltsp
13:29bytor4232 has left #ltsp
13:30
<warren>
that was interesting.
13:30
that was interesting.
13:31
<yallax_up>
Oo
13:31
Oo
13:31
<_UsUrPeR_>
warren: yes. it's Etherboot-5.0
13:31
warren: yes. it's Etherboot-5.0
13:31
<warren>
_UsUrPeR_: ok, then try the latest ltsp-server from my repo, and rebuild your chroot again
13:31
_UsUrPeR_: ok, then try the latest ltsp-server from my repo, and rebuild your chroot again
13:32
_UsUrPeR_: with the new default dhcpd.conf it should JUST WORK
13:32
_UsUrPeR_: with the new default dhcpd.conf it should JUST WORK
13:32
no manual configuration
13:32
no manual configuration
13:32
<_UsUrPeR_>
warren: what, seriously? Awesome!
13:32
warren: what, seriously? Awesome!
13:32* _UsUrPeR_ reads above
13:32* _UsUrPeR_ reads above
13:32
<_UsUrPeR_>
flpxj
13:32
flpxj
13:35
warren: ok, just installed the ltsp-server-5.1.19-1.i386.rpm
13:35
warren: ok, just installed the ltsp-server-5.1.19-1.i386.rpm
13:36
warren: so is this going to keep the bridge?
13:36
warren: so is this going to keep the bridge?
13:36
<warren>
_UsUrPeR_: it should, you screwed that up yourself somehow last time.
13:36
_UsUrPeR_: it should, you screwed that up yourself somehow last time.
13:38
<_UsUrPeR_>
warren: I sure did :/
13:38
warren: I sure did :/
13:40
warren: ok, had to kill vmware due to another OS screwing up. I have just rebooted Fedora after installing your RPM
13:40
warren: ok, had to kill vmware due to another OS screwing up. I have just rebooted Fedora after installing your RPM
13:40
what is the next step?
13:40
what is the next step?
13:42
warren: in the interim, I have tried booting. It's not working and here is the error:
13:42
warren: in the interim, I have tried booting. It's not working and here is the error:
13:43
..Me: 172.31.100.100, Server: 172.31.100.254, Gateway 172.31.100.254
13:43
..Me: 172.31.100.100, Server: 172.31.100.254, Gateway 172.31.100.254
13:43
Loading 172.31.100.254:/var/lib/tftpboot/ltsp/i386/legacy-nbi.ltsp .TFTP error 1
13:43
Loading 172.31.100.254:/var/lib/tftpboot/ltsp/i386/legacy-nbi.ltsp .TFTP error 1
13:43
(File not found)
13:43
(File not found)
13:43
Unable to load file
13:43
Unable to load file
13:43
<sleep>
13:43
<sleep>
13:43
<warren>
_UsUrPeR_: wipe out your chroot and nistall it again
13:43
_UsUrPeR_: wipe out your chroot and nistall it again
13:45
<_UsUrPeR_>
ok, doing now
13:45
ok, doing now
13:45
ltsp-build-client --arch i386
13:45
ltsp-build-client --arch i386
13:45
<warren>
you don't need --arch i386
13:45
you don't need --arch i386
13:45
it defaults to i386 on i386 and x86_64 hosts
13:45
it defaults to i386 on i386 and x86_64 hosts
13:45yallax_on has quit IRC
13:45yallax_on has quit IRC
13:45
<_UsUrPeR_>
warren: oh. I got used to that when working with suse
13:45
warren: oh. I got used to that when working with suse
13:47yallax_up has quit IRC
13:47yallax_up has quit IRC
13:51
<johnny>
yeah, i did that too warren
13:51
yeah, i did that too warren
13:52
ogra, did you end up opting that way?
13:52
ogra, did you end up opting that way?
13:52
for intrepid*
13:52
for intrepid*
13:53
<warren>
ltsp-trunk/server/plugins/ltsp-build-client/common/001-set-arch is not common
13:53
ltsp-trunk/server/plugins/ltsp-build-client/common/001-set-arch is not common
13:53
everyone overrides it in their own way.
13:53
everyone overrides it in their own way.
13:53
we might as well delete it
13:53
we might as well delete it
13:54
<johnny>
if it would work for x86.. i'd use it
13:54
if it would work for x86.. i'd use it
13:54
we don't use i386
13:54
we don't use i386
13:56fsgaston2 has joined #ltsp
13:56fsgaston2 has joined #ltsp
13:57
<fsgaston2>
If you have 12 classroom and 7 servers, how to you have a classroom only see one printer in LTSP 5
13:57
If you have 12 classroom and 7 servers, how to you have a classroom only see one printer in LTSP 5
13:59GodFather has joined #ltsp
13:59GodFather has joined #ltsp
13:59Blinny has quit IRC
13:59Blinny has quit IRC
14:00
<_UsUrPeR_>
warren: etyack wants to know the location of your instructions
14:00
warren: etyack wants to know the location of your instructions
14:04
<gbolte>
fsgaston2, setting the default printer dosent work for the users of each classroom?
14:04
fsgaston2, setting the default printer dosent work for the users of each classroom?
14:05
or you want to make it so only particular classrooms can use a printer?
14:05
or you want to make it so only particular classrooms can use a printer?
14:05
may need to play with printer permissions in CUPS
14:05
may need to play with printer permissions in CUPS
14:09
<warren>
_UsUrPeR_: instructions for that?
14:09
_UsUrPeR_: instructions for that?
14:11
<_UsUrPeR_>
warren: yeah. you had said yesterday that there was instructions I should be following, but I didn't see anything on your site pertaining to that. Did I miss a URL somewhere?
14:11
warren: yeah. you had said yesterday that there was instructions I should be following, but I didn't see anything on your site pertaining to that. Did I miss a URL somewhere?
14:12
<gbolte>
fsgaston2, there is an allowed users list per each printer in my cups web interface I assume that is what you would need to do to manage who can print where
14:12
fsgaston2, there is an allowed users list per each printer in my cups web interface I assume that is what you would need to do to manage who can print where
14:12
:D
14:12
:D
14:12
<warren>
_UsUrPeR_: https://fedorahosted.org/k12linux/wiki/NetworkSetup this mentions things that would have avoided your problem
14:12
_UsUrPeR_: https://fedorahosted.org/k12linux/wiki/NetworkSetup this mentions things that would have avoided your problem
14:12
i suppose it needs reorg
14:12
i suppose it needs reorg
14:17
<_UsUrPeR_>
warren: ok, finished creating a new environment.
14:17
warren: ok, finished creating a new environment.
14:18
<warren>
_UsUrPeR_: is the /etc/ltsp/dhcpd.conf the default shipped in ltsp-server-5.1.19?
14:18
_UsUrPeR_: is the /etc/ltsp/dhcpd.conf the default shipped in ltsp-server-5.1.19?
14:18
<_UsUrPeR_>
warren: testing, no dice. giving the same error as above
14:18
warren: testing, no dice. giving the same error as above
14:18
<warren>
you might need to restart ltsp-dhcpd
14:18
you might need to restart ltsp-dhcpd
14:21
<_UsUrPeR_>
warren: eureka! That's a lot of dots...
14:21
warren: eureka! That's a lot of dots...
14:22
<warren>
_UsUrPeR_: does it actually boot after the dots?
14:22
_UsUrPeR_: does it actually boot after the dots?
14:22
<_UsUrPeR_>
warren: ok, now it prints out a ton of dots, comes to the end and says "Unable to load file."
14:22
warren: ok, now it prints out a ton of dots, comes to the end and says "Unable to load file."
14:22
warren: then it prints more dotsthen it
14:22
warren: then it prints more dotsthen it
14:22
<warren>
_UsUrPeR_: what nbi filenames is it pointing at in /etc/ltsp/dhcpd.conf?
14:22
_UsUrPeR_: what nbi filenames is it pointing at in /etc/ltsp/dhcpd.conf?
14:23
<_UsUrPeR_>
"/ltsp/i386/legacy-nbi.ltsp"
14:23
"/ltsp/i386/legacy-nbi.ltsp"
14:24
<warren>
_UsUrPeR_: is there a /etc/ltsp/dhcpd.conf.rpmnew?
14:24
_UsUrPeR_: is there a /etc/ltsp/dhcpd.conf.rpmnew?
14:25
_UsUrPeR_: you didn't replace the old dhcpd.conf. if you modified a config file it wont upgrade it to the new version.
14:25
_UsUrPeR_: you didn't replace the old dhcpd.conf. if you modified a config file it wont upgrade it to the new version.
14:25
_UsUrPeR_: just move it over, restart the service again
14:25
_UsUrPeR_: just move it over, restart the service again
14:26
<_UsUrPeR_>
there is an rpmnew
14:26
there is an rpmnew
14:28
by "restart the service" you eant me to /etc/init.d/ltsp-dhcpd restart?
14:28
by "restart the service" you eant me to /etc/init.d/ltsp-dhcpd restart?
14:28
after moving the filename
14:28
after moving the filename
14:28
just did that, it didn't re-create anything
14:28
just did that, it didn't re-create anything
14:29
there we go. I got it
14:29
there we go. I got it
14:30
warren: ok, ok. Tell erick to stop hitting me
14:30
warren: ok, ok. Tell erick to stop hitting me
14:30
warren: we're all set. this looks great.
14:30
warren: we're all set. this looks great.
14:31
<warren>
_UsUrPeR_: you're actaully there with eryck?
14:31
_UsUrPeR_: you're actaully there with eryck?
14:31
<_UsUrPeR_>
I work for him
14:31
I work for him
14:31
<warren>
oh
14:31
oh
14:32
_UsUrPeR_: well, you can tell him one of the ancinet clients he sent me is credited for fixing this.
14:32
_UsUrPeR_: well, you can tell him one of the ancinet clients he sent me is credited for fixing this.
14:32
<_UsUrPeR_>
etyack says you're welcome1
14:32
etyack says you're welcome1
14:35leio has quit IRC
14:35leio has quit IRC
14:38Lns has quit IRC
14:38Lns has quit IRC
14:39
<etyack>
warren: the rpm you had _UsUrPeR_ work with, do you recommend using it on a production server? Or is this slated for more testing and FC 10?
14:39
warren: the rpm you had _UsUrPeR_ work with, do you recommend using it on a production server? Or is this slated for more testing and FC 10?
14:40
<warren>
etyack: if no problems are found, i'm going to rebuild it with no changes and push it into Fedora 9 updates.
14:40
etyack: if no problems are found, i'm going to rebuild it with no changes and push it into Fedora 9 updates.
14:40
<etyack>
warren: any idea of time frame?
14:40
warren: any idea of time frame?
14:41
<warren>
etyack: maybe a week, I want to do a lot more testing
14:41
etyack: maybe a week, I want to do a lot more testing
14:41
etyack: I might add more minor unrelated fixes though
14:41
etyack: I might add more minor unrelated fixes though
14:42
etyack: what kind of hardware is that client with old etherboot?
14:42
etyack: what kind of hardware is that client with old etherboot?
14:42
etyack: I got it working last night with a Jammin-125
14:42
etyack: I got it working last night with a Jammin-125
14:43
<etyack>
ltsp term 150/tk-3350 via based client
14:43
ltsp term 150/tk-3350 via based client
14:44
wow jammin-125! does the video work well? the nsc ship has been a real problem.
14:44
wow jammin-125! does the video work well? the nsc ship has been a real problem.
14:44
if you have a 150/tk-3350 it may not use Etherboot
14:44
if you have a 150/tk-3350 it may not use Etherboot
14:45
<warren>
etyack: no, the upstream nsc driver has been broken in xorg 1.5
14:45
etyack: no, the upstream nsc driver has been broken in xorg 1.5
14:45
etyack: waiting on someone to merge the old nsc driver into the geode driver.
14:45
etyack: waiting on someone to merge the old nsc driver into the geode driver.
14:45
etyack: the merge will also allow GX2 to be autodetected, currently upstream refuses to allow it
14:45
etyack: the merge will also allow GX2 to be autodetected, currently upstream refuses to allow it
14:46The_Code has quit IRC
14:46The_Code has quit IRC
14:46
<warren>
etyack: any progress on getting atom? I've been playing with it lately as a thin client. it is indeed awesome.
14:46
etyack: any progress on getting atom? I've been playing with it lately as a thin client. it is indeed awesome.
14:46
etyack: Intel 945 video and 1.6GHz proc
14:46
etyack: Intel 945 video and 1.6GHz proc
14:47triaxe has joined #ltsp
14:47triaxe has joined #ltsp
14:48
<etyack>
warren: nothing yet. we have 6 new thin clients to test, but nothing atom based, all via
14:48
warren: nothing yet. we have 6 new thin clients to test, but nothing atom based, all via
14:48
sorry, one is amd - thin-can
14:48
sorry, one is amd - thin-can
14:48
<triaxe>
we are on a university, and use xubuntu ltsp servers.. ubuntu/xubuntu seems to set the permission rw-r-r on all new users home folders.. is there a login script or somthing that can set /home/username to rw----(0700) ?
14:48
we are on a university, and use xubuntu ltsp servers.. ubuntu/xubuntu seems to set the permission rw-r-r on all new users home folders.. is there a login script or somthing that can set /home/username to rw----(0700) ?
14:48
<warren>
etyack: hopefully Harald Welte now working for VIA will make them suck less...
14:48
etyack: hopefully Harald Welte now working for VIA will make them suck less...
14:49
<etyack>
suck less is good...,
14:49
suck less is good...,
14:49
<_UsUrPeR_>
etyack: that booted fine too
14:49
etyack: that booted fine too
14:50
<etyack>
great!
14:50
great!
14:50The_Code has joined #ltsp
14:50The_Code has joined #ltsp
14:52
<warren>
vagrantc: so I seriously can't rely on /usr/bin/chvt?
14:52
vagrantc: so I seriously can't rely on /usr/bin/chvt?
14:52
vagrantc: us other distros seem to have /usr/bin/chvt
14:52
vagrantc: us other distros seem to have /usr/bin/chvt
14:55
<vagrantc>
warren: debian has it too, but it also has /bin/chvt.
14:55
warren: debian has it too, but it also has /bin/chvt.
14:56
warren: if it's so abhorrent, i can patch around it in debian.
14:56
warren: if it's so abhorrent, i can patch around it in debian.
14:56
<warren>
vagrantc: I'll just do the PATH thing again...
14:56
vagrantc: I'll just do the PATH thing again...
14:56
<johnny>
/usr/bin/chvt here..
14:56
/usr/bin/chvt here..
14:59
<gbolte>
/bin/chvt here
14:59
/bin/chvt here
14:59
<vagrantc>
so, i've got this wonderful user who wants tcsh to work with ldm ... i've got a patch for ldm 2.0.6 and it shouldn't be hard to forward port that to current upstream ...
14:59
so, i've got this wonderful user who wants tcsh to work with ldm ... i've got a patch for ldm 2.0.6 and it shouldn't be hard to forward port that to current upstream ...
15:00
it basically amounts to pre-pending "env" to our LDM ssh calls.
15:00
it basically amounts to pre-pending "env" to our LDM ssh calls.
15:00
anything that calls ssh via the tunnel would also probably have to do so.
15:00
anything that calls ssh via the tunnel would also probably have to do so.
15:00
and then switching the "kill -1 $PPID" approach to "exec sh kill -1 $PPID"
15:00
and then switching the "kill -1 $PPID" approach to "exec sh kill -1 $PPID"
15:01
since $PPID isn't available as a variable in tcsh ...
15:01
since $PPID isn't available as a variable in tcsh ...
15:01
so the question comes down to: do we refuse to support tcsh in ldm?
15:01
so the question comes down to: do we refuse to support tcsh in ldm?
15:03
http://bugs.debian.org/490897
15:03
http://bugs.debian.org/490897
15:03
i guess i should post to the list about it...
15:03
i guess i should post to the list about it...
15:06
<johnny>
warren, it'd be nice to have a slackware person around to ask such things to
15:06
warren, it'd be nice to have a slackware person around to ask such things to
15:06
<etyack>
warren: in ltsp 4.2, lts.conf used "like" where you specified a client hardware/option configuration and then could apply it to additional clients using "LIKE = ". Is that capability available in FC9 w/LTSP 5?
15:06
warren: in ltsp 4.2, lts.conf used "like" where you specified a client hardware/option configuration and then could apply it to additional clients using "LIKE = ". Is that capability available in FC9 w/LTSP 5?
15:06
<warren>
vagrantc: IMHO, no.
15:06
vagrantc: IMHO, no.
15:07
vagrantc: (t)csh are effectively different languages than *ash
15:07
vagrantc: (t)csh are effectively different languages than *ash
15:07
<Gadi>
etyack: yes
15:07
etyack: yes
15:07
<etyack>
Gadi: thanks
15:07
Gadi: thanks
15:07
<Gadi>
and hi
15:07
and hi
15:07
:)
15:07
:)
15:07
<warren>
etyack: I never understood the like option
15:07
etyack: I never understood the like option
15:07
<etyack>
howdy
15:07
howdy
15:07
<warren>
etyack: we're using the same lts.conf parser in fedora as ltsp-trunk and all the other distros
15:07
etyack: we're using the same lts.conf parser in fedora as ltsp-trunk and all the other distros
15:07
<Gadi>
warren: don't you touch my LIKE option - I need that ;)
15:07
warren: don't you touch my LIKE option - I need that ;)
15:07
<etyack>
we are helping a client transition to fc9 ltsp 5 and they used it ALOT
15:07
we are helping a client transition to fc9 ltsp 5 and they used it ALOT
15:07
<vagrantc>
warren: well i know it's a different language, but if a user wants tcsh as their default shell, it seems a bit restrictive to say you must use a bourne-derived shell...
15:07
warren: well i know it's a different language, but if a user wants tcsh as their default shell, it seems a bit restrictive to say you must use a bourne-derived shell...
15:08
<etyack>
warren: thanks
15:08
warren: thanks
15:08
<johnny>
does it work like SQL LIKE? :)
15:08
does it work like SQL LIKE? :)
15:08
<Gadi>
johnny: no
15:08
johnny: no
15:08
:)
15:08
:)
15:08
<warren>
default shell != shell used in the scripts
15:08
default shell != shell used in the scripts
15:08
<vagrantc>
warren: agreed.
15:08
warren: agreed.
15:08
<warren>
and anybody using tcsh as their default shell is just insane
15:08
and anybody using tcsh as their default shell is just insane
15:09
<Gadi>
amen! down with emacs
15:09
amen! down with emacs
15:09
long live vi
15:09
long live vi
15:09
<warren>
yay
15:09
yay
15:09
<vagrantc>
warren: if a user sets their default shell to tcsh, because of some of the assumptions we made with ldm, it fails to login.
15:09
warren: if a user sets their default shell to tcsh, because of some of the assumptions we made with ldm, it fails to login.
15:09
<johnny>
down with vimacs!
15:09
down with vimacs!
15:09
<warren>
vagrantc: that is a bug we need to fix in our code then.
15:09
vagrantc: that is a bug we need to fix in our code then.
15:09
<vagrantc>
ok. i'll post to the list about it.
15:09
ok. i'll post to the list about it.
15:09Lns has joined #ltsp
15:09Lns has joined #ltsp
15:09
<warren>
vagrantc: but it is completely unreasonable to add stuff to every script to support an entirely different language
15:09
vagrantc: but it is completely unreasonable to add stuff to every script to support an entirely different language
15:10
our /etc/profile.d has two sets of scripts for *ash and *csh
15:10
our /etc/profile.d has two sets of scripts for *ash and *csh
15:10
because they are different languages
15:10
because they are different languages
15:10The_Code has quit IRC
15:10The_Code has quit IRC
15:11
<vagrantc>
warren: well, for ldm 2.0.6 it looks like a 3 line patch, and probably comparable for current ldm-trunk.
15:11
warren: well, for ldm 2.0.6 it looks like a 3 line patch, and probably comparable for current ldm-trunk.
15:11
<warren>
vagrantc: this sets a bad precedent though
15:11
vagrantc: this sets a bad precedent though
15:11
vagrantc: we're restricted in the language we use in scripts
15:11
vagrantc: we're restricted in the language we use in scripts
15:13
<vagrantc>
warren: i don't think it will be a lot of changes, but yes, it could get ugly in the future.
15:13
warren: i don't think it will be a lot of changes, but yes, it could get ugly in the future.
15:14
<warren>
vagrantc: that person has /bin/sh linked to tcsh?
15:14
vagrantc: that person has /bin/sh linked to tcsh?
15:14
that would break so many other things
15:14
that would break so many other things
15:14
we really can't be responsible if that is the case
15:14
we really can't be responsible if that is the case
15:14
<vagrantc>
warren: no, their user's default shell is /bin/tcsh
15:14
warren: no, their user's default shell is /bin/tcsh
15:15
i.e. chsh -s /bin/tcsh USER
15:15
i.e. chsh -s /bin/tcsh USER
15:15
<warren>
ok
15:15
ok
15:15
can we make sure our scripts run as /bin/sh?
15:15
can we make sure our scripts run as /bin/sh?
15:15
<vagrantc>
posted to the list just now.
15:15
posted to the list just now.
15:15
<warren>
I'm 100% against adding things that make csh syntax work
15:15
I'm 100% against adding things that make csh syntax work
15:15
<vagrantc>
agreed.
15:15
agreed.
15:15
<warren>
I'm for making sure scripts run with /bin/sh
15:15
I'm for making sure scripts run with /bin/sh
15:15
<Gadi>
+1
15:15
+1
15:15triaxe has quit IRC
15:15triaxe has quit IRC
15:15
<warren>
oh, there's lots of syntax that is different between csh and tcsh too.
15:15
oh, there's lots of syntax that is different between csh and tcsh too.
15:15
it is a mess
15:15
it is a mess
15:16
<vagrantc>
well, this is basically just how to set variables on the commandline.
15:16
well, this is basically just how to set variables on the commandline.
15:16fsgaston2 has quit IRC
15:16fsgaston2 has quit IRC
15:16
<vagrantc>
and the $PPID variable's lack of existance.
15:16
and the $PPID variable's lack of existance.
15:16
which is kind of hacky and we'd like to get rid of anyways.
15:16
which is kind of hacky and we'd like to get rid of anyways.
15:20
<Gadi>
vagrantc: btw - what process was not letting things log out with ssh -O again?
15:20
vagrantc: btw - what process was not letting things log out with ssh -O again?
15:20
<warren>
it was variable I think
15:20
it was variable I think
15:20
<Gadi>
was it something that dissociated from the sshd process?
15:20
was it something that dissociated from the sshd process?
15:20
<warren>
Gadi: any progress on splitting X out?
15:20
Gadi: any progress on splitting X out?
15:20
<vagrantc>
Gadi: icewm was the window manager, and it was dbus that was hanging
15:20
Gadi: icewm was the window manager, and it was dbus that was hanging
15:21
<Gadi>
warren: you'll be the first to know
15:21
warren: you'll be the first to know
15:21
:)
15:21
:)
15:21
<vagrantc>
Gadi: or, dbus-launch
15:21
Gadi: or, dbus-launch
15:21
<Gadi>
vagrantc: did sshd die but not dbus?
15:21
vagrantc: did sshd die but not dbus?
15:21
or was sshd still running?
15:21
or was sshd still running?
15:21
<vagrantc>
sshd would still run
15:21
sshd would still run
15:22
<Gadi>
interesting
15:22
interesting
15:22
could I propose something?
15:22
could I propose something?
15:23
<moquist_>
ogra (or anyone): I used to use ramdisk_size=32000 root=/dev/rd0 rw nfsroot=10.2.1.1:/opt/ltsp/i386 in my PXE config to boot TCs to LTSP servers with NFS TC roots. How can I boot to an LTSP server using an NBD root?
15:23
ogra (or anyone): I used to use ramdisk_size=32000 root=/dev/rd0 rw nfsroot=10.2.1.1:/opt/ltsp/i386 in my PXE config to boot TCs to LTSP servers with NFS TC roots. How can I boot to an LTSP server using an NBD root?
15:23
<vagrantc>
i haven't tried it with -O exit on the same call, but i'm really skeptical if that'll work any better, as the command won't complete.
15:23
i haven't tried it with -O exit on the same call, but i'm really skeptical if that'll work any better, as the command won't complete.
15:23
<Gadi>
I bet we could take out both ssh -O and kill.... and create two kill rc.d scripts
15:23
I bet we could take out both ssh -O and kill.... and create two kill rc.d scripts
15:23
98sshO
15:23
98sshO
15:23
99sshKill
15:23
99sshKill
15:23
<warren>
monteslu: ramdisk_size is for what?
15:23
monteslu: ramdisk_size is for what?
15:23
oops
15:23
oops
15:23
<Gadi>
er, 98KsshO
15:23
er, 98KsshO
15:23
<warren>
moquist_: ^^
15:23
moquist_: ^^
15:23
<Gadi>
99KsshKill
15:23
99KsshKill
15:23
<vagrantc>
Gadi: the problem is that the ssh Xsession bit never finishes
15:23
Gadi: the problem is that the ssh Xsession bit never finishes
15:23
<warren>
Gadi: do those scripts actually run?
15:23
Gadi: do those scripts actually run?
15:24
<vagrantc>
Gadi: so no additional scripts would be run
15:24
Gadi: so no additional scripts would be run
15:24
<Gadi>
but, it must finish, because otherwise ;kill would not be called
15:24
but, it must finish, because otherwise ;kill would not be called
15:25
<moquist_>
warren: heh; it's been a long time since I set that up...I think the kernel needed to be told to create a ramdisk, else it didn't. Beats me why a PXE config on a remote server is different than on the LTSP server...
15:25
warren: heh; it's been a long time since I set that up...I think the kernel needed to be told to create a ramdisk, else it didn't. Beats me why a PXE config on a remote server is different than on the LTSP server...
15:25
<vagrantc>
the command finishes, but the tunnel doesn't close because it's got stuff running
15:25
the command finishes, but the tunnel doesn't close because it's got stuff running
15:25
<Gadi>
right
15:25
right
15:25
so if ssh -O does not kill it (98)
15:25
so if ssh -O does not kill it (98)
15:25
<vagrantc>
that's why kill works.
15:25
that's why kill works.
15:25
<moquist_>
more to the point now, I need some way to tell my kernel where to find its NBD root.
15:25
more to the point now, I need some way to tell my kernel where to find its NBD root.
15:25
<Gadi>
then, ssh kill $PPID (99) would
15:25
then, ssh kill $PPID (99) would
15:26
<vagrantc>
Gadi: enough talk, time for testing.
15:26
Gadi: enough talk, time for testing.
15:26
<Gadi>
but, it would kill it after running through all the kill scripts
15:26
but, it would kill it after running through all the kill scripts
15:26
:)
15:26
:)
15:26
<moquist_>
the PXE config on hardy says "DEFAULT vmlinuz ro initrd=initrd.img quiet splash", and I don't understand how the kernel knows where to find root.
15:26
the PXE config on hardy says "DEFAULT vmlinuz ro initrd=initrd.img quiet splash", and I don't understand how the kernel knows where to find root.
15:27
(I don't think I really understood that with NFS roots either, but it's been over a year since I've thought about it.)
15:27
(I don't think I really understood that with NFS roots either, but it's been over a year since I've thought about it.)
15:27japerry_cat has joined #ltsp
15:27japerry_cat has joined #ltsp
15:27moquist_ is now known as moquist
15:27moquist_ is now known as moquist
15:29
<johnny>
moquist, it can get the root path from the server
15:29
moquist, it can get the root path from the server
15:29
via dhcp
15:29
via dhcp
15:29plamengr has quit IRC
15:29plamengr has quit IRC
15:30
<moquist>
johnny: *doh* It's been so long...
15:30
johnny: *doh* It's been so long...
15:31
<Gadi>
moquist: default is LTSP server and port 2000
15:31
moquist: default is LTSP server and port 2000
15:31
you can specify kernel param: nbdroot=<IP:2000>
15:31
you can specify kernel param: nbdroot=<IP:2000>
15:31
<moquist>
Gadi: how can I pass something on the kernel cmd line to change the default. .. yay!
15:31
Gadi: how can I pass something on the kernel cmd line to change the default. .. yay!
15:31
<Nick_Hill>
I am just re-installing on totally different hardware, but has anyone else experienced a bug where you cannot log into a new user account through the thin client until the server has been rebooted? Ubuntu/8.04
15:31
I am just re-installing on totally different hardware, but has anyone else experienced a bug where you cannot log into a new user account through the thin client until the server has been rebooted? Ubuntu/8.04
15:32
<vagrantc>
Gadi: ok, so, what do you propose to change?
15:32
Gadi: ok, so, what do you propose to change?
15:32
<Gadi>
I am proposing, taking out the kill call
15:32
I am proposing, taking out the kill call
15:32
and do both kinds of kills in rc.d
15:32
and do both kinds of kills in rc.d
15:32
sshO first
15:32
sshO first
15:32
sshKill second
15:32
sshKill second
15:33
so: rc.d/K98-sshO
15:33
so: rc.d/K98-sshO
15:33
<moquist>
I have 25 minutes before I have to leave, and I won't be back in the office until the kids start school on the 27th. Now I can continue working remotely on our LTSP servers (because I can boot VMs to various different LTSP servers in different subnets).
15:33
I have 25 minutes before I have to leave, and I won't be back in the office until the kids start school on the 27th. Now I can continue working remotely on our LTSP servers (because I can boot VMs to various different LTSP servers in different subnets).
15:33
Gadi, johnny, warren: thanks!
15:33
Gadi, johnny, warren: thanks!
15:33
<Gadi>
vagrantc: and, rc.d/K99-sshKill
15:33
vagrantc: and, rc.d/K99-sshKill
15:33
moquist: np
15:33
moquist: np
15:34
K98-sshO: ssh ... -S ... -O exit
15:34
K98-sshO: ssh ... -S ... -O exit
15:34
K99-sshKill: ssh ... -S ... 'kill -1 ${PPID}'
15:34
K99-sshKill: ssh ... -S ... 'kill -1 ${PPID}'
15:35
<vagrantc>
Gadi: in the rc.d directories?
15:35
Gadi: in the rc.d directories?
15:35warren has quit IRC
15:35warren has quit IRC
15:36
<Gadi>
yeah
15:36
yeah
15:36* vagrantc commits acts of evil .... mv kill kill.orig ; ln -s /bin/true kill
15:36* vagrantc commits acts of evil .... mv kill kill.orig ; ln -s /bin/true kill
15:37
<Gadi>
yikes - why?
15:37
yikes - why?
15:37
<vagrantc>
so i don't have to re-build ldm :)
15:37
so i don't have to re-build ldm :)
15:37
<Gadi>
but, you still need kill
15:37
but, you still need kill
15:37
:)
15:37
:)
15:37elisboa has quit IRC
15:37elisboa has quit IRC
15:37Q-FUNK has quit IRC
15:37Q-FUNK has quit IRC
15:37
<Gadi>
unless you move it somewhere else
15:37
unless you move it somewhere else
15:37
<vagrantc>
kill.orig will come in handy.
15:37
kill.orig will come in handy.
15:37
<Gadi>
ok
15:37
ok
15:37
u are evil
15:37
u are evil
15:38
<vagrantc>
it's just a hackish test ... if it works, i'll actually do it more properly.
15:38
it's just a hackish test ... if it works, i'll actually do it more properly.
15:38
<Gadi>
but only because you "live backwards"
15:38
but only because you "live backwards"
15:38
har har har
15:38
har har har
15:43japerry has quit IRC
15:43japerry has quit IRC
15:46leio has joined #ltsp
15:46leio has joined #ltsp
15:46
<vagrantc>
oh hell. kill is a shell builtin.
15:46
oh hell. kill is a shell builtin.
15:46
GAH.
15:46
GAH.
15:47bobby_C has joined #ltsp
15:47bobby_C has joined #ltsp
15:47
<johnny>
but is it built in tcsh .. har har :)
15:47
but is it built in tcsh .. har har :)
15:47mccann has quit IRC
15:47mccann has quit IRC
15:49etyack has left #ltsp
15:49etyack has left #ltsp
15:50
<vagrantc>
Gadi: "ssh -O exit blah blah blah true" is actually hanging
15:50
Gadi: "ssh -O exit blah blah blah true" is actually hanging
15:51
<Gadi>
what the blah?
15:51
what the blah?
15:51
it should just be: ssh -S <socket> -O exit
15:51
it should just be: ssh -S <socket> -O exit
15:51
oh, and server
15:51
oh, and server
15:51
you don't need more than that
15:51
you don't need more than that
15:52
ssh -S ${LDM_SOCKET} -O exit ${LDM_SERVER}
15:52
ssh -S ${LDM_SOCKET} -O exit ${LDM_SERVER}
15:52
<vagrantc>
will try
15:52
will try
15:54
<sutula>
vagrantc: I haven't been paying attention lately. :( How are the Lenny (frozen) ltsp bits these days? Are they pretty clean, or will installations want to continue with a -backports version?
15:54
vagrantc: I haven't been paying attention lately. :( How are the Lenny (frozen) ltsp bits these days? Are they pretty clean, or will installations want to continue with a -backports version?
15:56
<vagrantc>
sutula: i'm overall pretty happy with them.
15:56
sutula: i'm overall pretty happy with them.
15:56
sutula: only thing missing is localapps, which actually doesn't require an actual backport to implement.
15:56
sutula: only thing missing is localapps, which actually doesn't require an actual backport to implement.
15:57
<sutula>
OK...I've been watching the -release mailing list and haven't seen any pleas from you :)
15:57
OK...I've been watching the -release mailing list and haven't seen any pleas from you :)
15:57
<vagrantc>
sutula: there was a significant rewrite of ldm, but it was basically re-writting the same weekend of the freeze, so i'm hesitant to push it.
15:57
sutula: there was a significant rewrite of ldm, but it was basically re-writting the same weekend of the freeze, so i'm hesitant to push it.
15:57
<sutula>
The RM's frown on that
15:57
The RM's frown on that
15:57mccann has joined #ltsp
15:57mccann has joined #ltsp
15:58
<vagrantc>
sutula: might get one or two more patches in, but overall, i think lenny's ltsp is looking pretty good.
15:58
sutula: might get one or two more patches in, but overall, i think lenny's ltsp is looking pretty good.
15:58
<sutula>
It's hard for packages that are still very much in development, but then, that's what -backports is for
15:58
It's hard for packages that are still very much in development, but then, that's what -backports is for
15:59_UsUrPeR_ has quit IRC
15:59_UsUrPeR_ has quit IRC
15:59
<sutula>
vagrantc: Anyway, thanks for the update
15:59
vagrantc: Anyway, thanks for the update
16:00
<vagrantc>
sutula: i'm sure someday something will come along where i'll want to start doing backports again :)
16:00
sutula: i'm sure someday something will come along where i'll want to start doing backports again :)
16:00Nick_Hill has quit IRC
16:00Nick_Hill has quit IRC
16:11
<vagrantc>
Gadi: still seems to hang...
16:11
Gadi: still seems to hang...
16:11
Gadi: though the command executes
16:11
Gadi: though the command executes
16:11
<Gadi>
do both commands execute?
16:11
do both commands execute?
16:11
(the ssh kill one, too?)
16:11
(the ssh kill one, too?)
16:13
<vagrantc>
it hangs on "ssh -O exit ..."
16:13
it hangs on "ssh -O exit ..."
16:13
but it actually executes it ...
16:13
but it actually executes it ...
16:14
<Gadi>
thats odd
16:14
thats odd
16:14
is there anything in the logs/
16:14
is there anything in the logs/
16:14
<vagrantc>
i put stuff in the logs
16:14
i put stuff in the logs
16:14
but nothing meaningful
16:14
but nothing meaningful
16:14
i'll try and do this the proper way rather than use my evil kill workaround
16:14
i'll try and do this the proper way rather than use my evil kill workaround
16:15
<Gadi>
well, at this point, kill's not involved, right?
16:15
well, at this point, kill's not involved, right?
16:15
<vagrantc>
well, that's hard to say, because kill is a shell builtin
16:15
well, that's hard to say, because kill is a shell builtin
16:15
<Gadi>
ah
16:15
ah
16:20
<vagrantc>
having the rc.d/K* scripts attempting to use the ssh socket seems to stall the login
16:20
having the rc.d/K* scripts attempting to use the ssh socket seems to stall the login
16:20
and kill appears to be happening.
16:20
and kill appears to be happening.
16:20
so i'll rebuild ldm and try again.
16:20
so i'll rebuild ldm and try again.
16:20
stall the logout, rather.
16:20
stall the logout, rather.
16:21
so, i guess the rc.d/K* scripts are executed after the kill kicks in, and somehow before the socket is removed, but doesn't work because sshd is killed.
16:21
so, i guess the rc.d/K* scripts are executed after the kill kicks in, and somehow before the socket is removed, but doesn't work because sshd is killed.
16:21
that's my guess, at least.
16:21
that's my guess, at least.
16:26K_O-Gnom has quit IRC
16:26K_O-Gnom has quit IRC
16:29johnny has left #ltsp
16:29johnny has left #ltsp
16:32NickHill has joined #ltsp
16:32NickHill has joined #ltsp
16:33
<vagrantc>
hm.
16:33
hm.
16:33
i'm not exhibiting the same problems i was having before with icewm.
16:33
i'm not exhibiting the same problems i was having before with icewm.
16:33
not even using ssh -O
16:33
not even using ssh -O
16:41
hmmm... maybe something changed in lenny... or etch.
16:41
hmmm... maybe something changed in lenny... or etch.
16:41
hmmm... i am using openssh-server 5.1
16:41
hmmm... i am using openssh-server 5.1
16:58warren has joined #ltsp
16:58warren has joined #ltsp
16:59
<vagrantc>
yes, it's definitely an openssh-server issue.
16:59
yes, it's definitely an openssh-server issue.
16:59
with openssh-server 5.1, ssh -O exit works great.
16:59
with openssh-server 5.1, ssh -O exit works great.
16:59johnny has joined #ltsp
16:59johnny has joined #ltsp
17:00
<vagrantc>
so it looks like we need to conditionall add "kill -1 $PPID
17:00
so it looks like we need to conditionall add "kill -1 $PPID
17:00
" only if the version of openssh-server doesn't support it.
17:00
" only if the version of openssh-server doesn't support it.
17:03* vagrantc wonders how to figure that out
17:03* vagrantc wonders how to figure that out
17:04
<vagrantc>
Gadi: hear that? it works! with openssh-server 5.1
17:04
Gadi: hear that? it works! with openssh-server 5.1
17:05
<Gadi>
Yay!
17:05
Yay!
17:05* Gadi wonders if we know what version
17:05* Gadi wonders if we know what version
17:05
<Gadi>
:)
17:05
:)
17:06
ie, which one it starts breaking in
17:06
ie, which one it starts breaking in
17:06
<vagrantc>
well, 4.7p1-12 in debian lenny doesn't work
17:06
well, 4.7p1-12 in debian lenny doesn't work
17:06
so it'd have to be newer than that.
17:06
so it'd have to be newer than that.
17:07mhterres has quit IRC
17:07mhterres has quit IRC
17:11
<Gadi>
another mystery solved
17:11
another mystery solved
17:11
now, as long as we have the rc.d dir, I'd propose keeping as many post-session scripts in there as possible
17:11
now, as long as we have the rc.d dir, I'd propose keeping as many post-session scripts in there as possible
17:12
altho, keeping them on the commandline for the session does handle sudden turn-offs of client
17:12
altho, keeping them on the commandline for the session does handle sudden turn-offs of client
17:12
hmm...
17:12
hmm...
17:12juanpaul has joined #ltsp
17:12juanpaul has joined #ltsp
17:12
<Gadi>
maybe the kill scripts are useless in most cases, because we will always be concerned with improper logoffs
17:12
maybe the kill scripts are useless in most cases, because we will always be concerned with improper logoffs
17:15warren has quit IRC
17:15warren has quit IRC
17:15
<vagrantc>
hard to say, exactly.
17:15
hard to say, exactly.
17:16
Gadi: the bad news is ... if we do both, the "ssh -O exit" hangs the session.
17:16
Gadi: the bad news is ... if we do both, the "ssh -O exit" hangs the session.
17:16
so we really hve to conditionally detect if it's worth doing.
17:16
so we really hve to conditionally detect if it's worth doing.
17:18
<Gadi>
crap
17:18
crap
17:19
does "ssh -O check" work?
17:19
does "ssh -O check" work?
17:19
or does it also hang?
17:19
or does it also hang?
17:19* vagrantc checks.
17:19* vagrantc checks.
17:21GodFather has quit IRC
17:21GodFather has quit IRC
17:23
<vagrantc>
Gadi: no luck on -O check ...
17:23
Gadi: no luck on -O check ...
17:23
what good is check if it hangs? :)
17:23
what good is check if it hangs? :)
17:24
<Gadi>
:)
17:24
:)
17:24
maybe there was different syntax in older version
17:24
maybe there was different syntax in older version
17:24
I dunno
17:24
I dunno
17:24
I gotta start heading out
17:24
I gotta start heading out
17:24
getting late
17:24
getting late
17:25
great work, tho, vagrantc
17:25
great work, tho, vagrantc
17:25
we're close
17:25
we're close
17:25
:)
17:25
:)
17:25
<vagrantc>
Gadi: thanks for your help on this! :)
17:25
Gadi: thanks for your help on this! :)
17:26
<Gadi>
cheer
17:26
cheer
17:26
s
17:26
s
17:26
:)
17:26
:)
17:26Gadi has left #ltsp
17:26Gadi has left #ltsp
17:26bobby_C has quit IRC
17:26bobby_C has quit IRC
17:34mccann has quit IRC
17:34mccann has quit IRC
18:20mikkel has quit IRC
18:20mikkel has quit IRC
18:28gbolte has quit IRC
18:28gbolte has quit IRC
18:29rjune has quit IRC
18:29rjune has quit IRC
18:32rjune has joined #ltsp
18:32rjune has joined #ltsp
18:37warren has joined #ltsp
18:37warren has joined #ltsp
18:57vagrantc has quit IRC
18:57vagrantc has quit IRC
19:14johnny has left #ltsp
19:14johnny has left #ltsp
19:53juanpaul has quit IRC
19:53juanpaul has quit IRC
20:00NickHill has quit IRC
20:00NickHill has quit IRC
20:07chupacabra has quit IRC
20:07chupacabra has quit IRC
20:09johnny2 has joined #ltsp
20:09johnny2 has joined #ltsp
21:10johnny2 has left #ltsp
21:10johnny2 has left #ltsp
21:10johnny has joined #ltsp
21:10johnny has joined #ltsp
21:13chupacabra has joined #ltsp
21:13chupacabra has joined #ltsp
21:28japerry_cat has quit IRC
21:28japerry_cat has quit IRC
22:37|Paradox| has joined #ltsp
22:37|Paradox| has joined #ltsp
22:56leio_ has joined #ltsp
22:56leio_ has joined #ltsp
23:00leio has quit IRC
23:00leio has quit IRC
23:00leio_ is now known as leio
23:00leio_ is now known as leio
23:16japerry has joined #ltsp
23:16japerry has joined #ltsp
23:40leio has quit IRC
23:40leio has quit IRC