|
From: not J. K. <jam...@ho...> - 2007-04-12 03:36:29
|
>On Wed, 11 Apr 2007 02:58:47 +0000 >"not James Knox" <jam...@ho...> wrote: > >Maybe its the wrong time. > >Idea: Start the computer. After bootup execute /etc/init.d/boot.local >manually and see, if irexec works. >If irexec runs it`s in the wrong place in boot.local. I tried running the line in boot.local, and it powered off my computer. So clearly this isn't a problem with the --daemon switch not working, it's probably a matter of boot.local being called before lircd starts. So where would be a better place to start irexec? I'm running Suse, and I don't quite know which order things get executed in. > >Sven > > > > > So how do you get irexec to start? It's possible that > > /etc/init.d/boot.local gets called at the wrong time. It's fine for > > bringing up my wireless Ethernet interface, or mounting a Samba share > > (which I haven't been able to do through any other means so far) but > > maybe it's the wrong time to start irexec. > > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share >your >opinions on IT & business topics through brief surveys-and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _________________________________________________________________ Dont waste time standing in linetry shopping online. Visit Sympatico / MSN Shopping today! http://shopping.sympatico.msn.ca |