[Openmcl-devel] Running CCL as a daemon

[Ron Garret]

Nothing is ever *supposed* to read from stdin.  But if you just launch a vanilla CCL it will create a listener which will attempt to read from stdin.

In a standard unix daemon, the stdin file descriptor is closed.  (So it stdout.)  I haven't actually tried this, but I suspect CCL will not be happy if that happens.

If you don't close stdin, even if you don't ever provide any input you still have to be aware of what it ends up being connected to because it's a potential security hole.

rg

On Feb 19, 2010, at 7:04 AM, Daniel Weinreb wrote:

> stdout and stderr are just sent to files.  The software
> isn't generally supposed to use them for anything.
> Nothing ever reads from stdin; it's just daemon software.
> 
> Ron Garret wrote:
>> 
>> But what do you do with stdin/stdout and the initial listener?
>> 
>> On Feb 18, 2010, at 8:48 AM, Daniel Weinreb wrote:
>> 
>>   
>>> We do that.
>>> -- Dan
>>> 
>>> Robert Goldman wrote:
>>>     
>>>> For a long-running daemon program we've worked on, we've compiled a
>>>> swank server into the program, so that one can attach a slime session.
>>>> Possibly worth investigating?
>>>> _______________________________________________
>>>> Openmcl-devel mailing list
>>>> Openmcl-devel at clozure.com
>>>> http://clozure.com/mailman/listinfo/openmcl-devel
>>>> 
>>>>       
>>> _______________________________________________
>>> Openmcl-devel mailing list
>>> Openmcl-devel at clozure.com
>>> http://clozure.com/mailman/listinfo/openmcl-devel
>>>     
>> 
>>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20100219/67a8026d/attachment.htm>