| 00:59.58 | *** join/#edev g1powermac (~g1powerma@rrcs-74-87-150-6.west.biz.rr.com) |
| 00:59.58 | *** join/#edev g1powermac (~g1powerma@unaffiliated/g1powermac) |
| 01:00.52 | *** join/#edev Belliash (~belliash@asiotec/constitutive/belliash) |
| 01:57.17 | *** join/#edev walltender (~nm@114.60.240.8) |
| 02:18.30 | *** join/#edev prpplague (~prpplague@107-206-64-184.lightspeed.rcsntx.sbcglobal.net) |
| 02:25.29 | *** mode/#edev [+o prpplague] by ChanServ |
| 02:39.01 | walltender | <PROTECTED> |
| 03:34.31 | *** join/#edev [7] (~quassel@rockbox/developer/TheSeven) |
| 04:34.55 | *** join/#edev djerome (~djerome@ip68-2-20-108.ph.ph.cox.net) |
| 04:36.41 | *** join/#edev ohama (ohama@cicolina.org) |
| 05:31.38 | _av500_ | walltender: the daemon can have a config file |
| 05:31.49 | _av500_ | user GUI changes it and send the daemon a signal to re-read it |
| 05:41.42 | *** join/#edev walltender (~nm@114.60.240.8) |
| 05:45.35 | *** join/#edev mbuf (user@nat/redhat/x-ewzhvrtuwfoexmrr) |
| 06:36.56 | *** join/#edev itdnhr (~quassel@74.63.212.44) |
| 06:49.43 | *** join/#edev megha (~fire@unaffiliated/security) |
| 06:51.14 | *** join/#edev itdnhr (~quassel@74.63.212.44) |
| 07:00.21 | *** join/#edev walltender (~nm@114.60.247.159) |
| 07:29.34 | *** join/#edev florian_kc (~fuchs@port-217-146-132-69.static.qsc.de) |
| 07:29.37 | *** join/#edev florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 08:03.49 | *** join/#edev darknighte (~darknight@pdpc/supporter/professional/darknighte) |
| 08:04.47 | *** join/#edev darknighte (~darknight@pdpc/supporter/professional/darknighte) |
| 10:16.39 | *** join/#edev itdnhr (~quassel@74.63.212.44) |
| 10:32.28 | *** join/#edev itdnhr (~quassel@74.63.212.44) |
| 10:44.24 | *** join/#edev walltender (~nm@114.60.244.150) |
| 10:52.03 | *** join/#edev kergoth (~kergoth@covenant.kergoth.com) |
| 10:59.33 | walltender | "A monitoring utility with different threads monitoring different devices, and those threads could be integrated into a monitor daemon and collect data in one or more files." Does it mean the daemon log all sensors data and spawn different threads for monitoring? |
| 11:03.10 | _av500_ | why do I have the impression you are fishing for homework? |
| 11:04.18 | gustavoz | sound an awful like what collectd already does |
| 11:04.21 | gustavoz | *sounds |
| 11:05.26 | walltender | Not homework, but a project. Please help. However, it's just part of it. |
| 11:08.43 | walltender | I don't understand that a daemon is not supposed to interact with users. However, part of the requirements is the user should be able to start/stop the monitoring threads, and set what action the utility will do when, for instance, temperature exceeds threshold. |
| 11:23.03 | *** join/#edev g1powermac (~g1powerma@unaffiliated/g1powermac) |
| 11:37.52 | jackmitchell | who says a daemon is not supposed to interact with users? |
| 11:38.08 | *** join/#edev vpopov (~happylife@37-147-202-203.broadband.corbina.ru) |
| 12:37.01 | firewall_tender | "Daemons should never have direct communication with a user through a terminal. In fact, a daemon shouldn't communicate directly with a user at all. All communication should pass through some sort of interface (which you may or may not have to write), which can be as complex as a GTK+ GUI, or as simple as a signal set." from http://www.netzmafia.de/skripten/unix/linux-daemon-howto.html. Actually, I don't quite understand why it can't directly interact w |
| 12:37.02 | firewall_tender | ith users? |
| 12:40.01 | _av500_ | how would it interact? |
| 12:40.06 | _av500_ | directly |
| 12:43.42 | firewall_tender | Well, perhaps I lack of some necessary knowledge? Would you mind enlight me? |
| 12:52.19 | firewall_tender | _av500_: Could you point out a direction to learn background process with user interaction? |
| 12:53.30 | _av500_ | well, background processes do not interact directly with users |
| 12:53.47 | _av500_ | like what you said above |
| 12:55.27 | firewall_tender | then how can it interact with user through GUI, or could you point to an example? |
| 13:00.11 | jackmitchell | firewall_tender: http://wordptr.com/2011/01/31/lets-write-a-linux-daemon-part-i/ |
| 13:00.29 | jackmitchell | that goes through the basics of a daemon and also has examples of how to configure daemons |
| 13:04.45 | firewall_tender | I have actually read several other beginner tutorial on daemon, my question is some tutorial on GUI interface to a daemon or how these a GUI can make settings for a daemon. |
| 13:07.22 | _av500_ | via e.g. config files |
| 13:07.36 | _av500_ | and then telling the daemon to re.read the config |
| 13:07.39 | _av500_ | with a signal |
| 13:07.49 | _av500_ | as I already said before |
| 13:08.37 | firewall_tender | _av500_ it might be a good idea, but I also want to learn it sysmatically, what shall I look up for such a problem? |
| 13:12.10 | _av500_ | I dont know |
| 13:12.20 | _av500_ | I'd have to google around |
| 13:15.10 | firewall_tender | _av500_: I can google around myself, but I must search for the wrong information, any suggestion? |
| 13:16.00 | *** join/#edev Anaphaxeton (~george@unaffiliated/anaphaxeton) |
| 13:41.03 | jackmitchell | firewall_tender: the link I posted tells you how to do that, just stick a gui on it and you're done |
| 13:48.15 | *** join/#edev g1powermac (~g1powerma@host-063-131-200-114.dhcp.fewpb.net) |
| 13:48.17 | *** join/#edev g1powermac (~g1powerma@unaffiliated/g1powermac) |
| 13:48.53 | firewall_tender | jackmitchell: I am reading that post. However, it's how to stick a gui to communicate with a daemon I am searching. Is it just a part of IPC topic? Or else? |
| 13:50.03 | jackmitchell | firewall_tender: well, just read a standard gui making tutorial, and then put that code in to control the daemon |
| 13:50.40 | jackmitchell | so pressing a button on the gui, might send a signal to the daemon which tells the daemon to do something |
| 13:51.43 | jackmitchell | I don't think you;re going to find a tutorial which covers writing a daemon, making a gui and then controlling the daemon with that gui..... we're not in Borland land here |
| 14:04.36 | firewall_tender | <jackmitchell> can daemon send signals back to GUI? |
| 14:05.50 | jackmitchell | firewall_tender: if you GUi is listening for signals then yes |
| 14:11.18 | dfarnsworth | <PROTECTED> |
| 14:20.58 | firewall_tender | dfarnsworth: it's a monitoring daemon that monitor all sensors. So I don't see socket or other IPC is better than using signal. However, I do have another question, "A monitoring utility with different threads monitoring different devices, and those threads could be integrated into a monitor daemon and collect data in one or more files." So I understand it as such a daemon log all sensors data and spawn different threads for monitoring as start? Then us |
| 14:20.58 | firewall_tender | er controls turning on/off monitoring threads through GUI. |
| 14:50.05 | *** join/#edev baba (~fire@unaffiliated/security) |
| 15:48.30 | *** join/#edev sndcrb (~sndcrb@cs181038038.pp.htv.fi) |
| 15:48.34 | *** join/#edev prpplague (~danders@adsl-68-88-69-181.dsl.rcsntx.swbell.net) |
| 15:50.22 | *** join/#edev arun (~arun@209-6-55-191.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com) |
| 15:50.22 | *** join/#edev arun (~arun@unaffiliated/sindian) |
| 15:57.31 | firewall_tender | What's argument for implement a daemon intergrate all others sensor monitoring threads which are created/destroyed upon user request through GUI interface? |
| 16:20.18 | *** join/#edev prpplague (~danders@adsl-68-88-69-181.dsl.rcsntx.swbell.net) |
| 16:20.46 | *** mode/#edev [+o prpplague] by ChanServ |
| 16:33.12 | *** join/#edev sndcrb (~sndcrb@cs181038038.pp.htv.fi) |
| 17:08.25 | *** join/#edev legov (~jonathan@friedpancakes.com) |
| 17:16.19 | *** join/#edev NightMonkey (~NightrMon@pdpc/supporter/professional/nightmonkey) |
| 17:24.33 | *** join/#edev prpplague (~danders@adsl-68-88-69-181.dsl.rcsntx.swbell.net) |
| 17:26.41 | *** mode/#edev [+o prpplague] by ChanServ |
| 17:29.10 | *** join/#edev prpplague (~danders@adsl-68-88-69-181.dsl.rcsntx.swbell.net) |
| 17:44.56 | *** join/#edev florian (~fuchs@sign-4db60e96.pool.mediaWays.net) |
| 17:44.57 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 18:19.32 | *** join/#edev itdnhr (~quassel@74.63.212.44) |
| 18:39.36 | *** join/#edev florian (~fuchs@89.204.139.175) |
| 18:39.36 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 19:01.20 | *** join/#edev florian (~fuchs@141.99.42.157) |
| 19:01.21 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 19:04.39 | *** join/#edev florian (~fuchs@141.99.42.157) |
| 19:04.39 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 19:25.04 | *** join/#edev _0bitcount (~ulises11@82.159.59.4.dyn.user.ono.com) |
| 19:59.38 | *** join/#edev florian (~fuchs@port-217-146-132-69.static.qsc.de) |
| 19:59.39 | *** join/#edev florian (~fuchs@Maemo/community/contributor/florian) |
| 22:13.46 | *** join/#edev gustavoz_ (~gustavoz@host147.190-138-228.telecom.net.ar) |
| 22:50.32 | *** join/#edev megha (~fire@unaffiliated/security) |
| 23:04.48 | *** join/#edev gustavoz (~gustavoz@host147.190-138-228.telecom.net.ar) |