On 10-12-14 10:14 AM, francescoboccacci at libero.it wrote:
> Hi,
> sorry if i have no insert a slonik version. I'm a new user of Slonik.
> My version is slon version 2.0.4 and i have postgresql 8.4 in my server.
> I run subscribe.sh in putty and now my question is:
> If i disconnect putty section what happend to my slonik process?
> Can i write these log rows into a log files?
> Thanks for your help.

If you exit putty the slons should continue to run disconnected from the 
terminal.

If you start the slon processes so that they redirect the standard 
output/error to a log file you can redirect them to a log file.



You can also get slon to log to syslog
http://www.slony.info/documentation/2.0/runtime-config.html



>
> Francesco
>
>> ----Messaggio originale----
>> Da: ssinger at ca.afilias.info
>> Data: 14/12/2010 15.58
>> A: "francescoboccacci at libero.it"<francescoboccacci at libero.it>
>> Cc:<slony1-general at lists.slony.info>
>> Ogg: Re: [Slony1-general] Slony message
>>
>> On 10-12-14 09:01 AM, francescoboccacci at libero.it wrote:
>>> Hi to all.
>>> I have some doubts about how slony-I replication process works.
>>> I Have one master and 4 slaves that share some tables.
>>> I create a cluster script and run it. After i run slon daemon in all
> nodes.
>>> At
>>> the end i run subscribe script. After this operation my server (linux)
> show
>>> messages but i don't undestand if this is normal or what are. After 2
> hours
>>> it
>>> still show me message like these:
>>>
>>
>> All of the messages below are normal messages from slony during normal
>> operations of slony.  I don't see any indication of a problem.
>>
>> If you connect to your slaves, do you see your data replicated?
>>
>> If your still having a problem look at what the
>> _sql_cluster_1_2_3_4_9.sl_status table contains.
>>
>> Also it is good practice to include which version of slony your using
>> when posting messages to the list.
>>
>>
>>
>>>
>>>
>>>
>>>
>>> NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: Logswitch to sl_log_1 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_1 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_1 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_1 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: Logswitch to sl_log_1 initiated
>>> CONTEXT:  SQL statement "SELECT  "_sql_cluster_1_2_3_4_9".
> logswitch_start()"
>>> PL/pgSQL function "cleanupevent" line 101 at PERFORM
>>> NOTICE:  Slony-I: log switch to sl_log_1 complete - truncate sl_log_2
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_1 complete - truncate sl_log_2
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_1 complete - truncate sl_log_2
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_1 complete - truncate sl_log_2
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>> NOTICE:  Slony-I: log switch to sl_log_1 complete - truncate sl_log_2
>>> CONTEXT:  PL/pgSQL function "cleanupevent" line 99 at assignment
>>>
>>> ..
>>> and so on.
>>> What happen? I need to restart some process or wait the end of the
> process?
>>>
>>> Please help me.
>>>
>>> Thanks to all
>>>
>>> Francesco
>>> _______________________________________________
>>> Slony1-general mailing list
>>> Slony1-general at lists.slony.info
>>> http://lists.slony.info/mailman/listinfo/slony1-general
>>
>>
>
>