🚀 go-pugleaf

In <33C3D8F5.3C60854C@isi-systems.de>, Juergen Goetz <goetz@isi-systems.de> writes:

]6:
]there is a prog installed on the server, which strips off older lines from
]the log-files to avoid HD-overflow. This is done by moving each single file
]to /tmp, throwing old lines away and moving the resulting file back to
]/clients/data/client[x]/.....
]The deleting program is involved by a script, which does a "sync;sync" before
]and after calling the deleting process.
]While deleting the log-files the 4 clients still continue writing to the server.

]Now what happens:

]After the deleting program / script running a while the four clients cant write
]to the server any more, hanging somehow. The writing process on each client does
]not work anymore, although mounted with "soft" option.
]You can "ping" to the server, but not "telnet" and there is no possibility to
]work on the server, because keyboard-input is not accepted. The are no entries
]on the server in .../messages or ..../syslog.

]I cant help myself.

I'm not surprised it doesn't work well. I'd not try archiving files 
    while they're in use. Sounds a sure way to get into trouble.
    
Try one of these: 

1  Do your file trimming for each client when they're not around.
2  Archive the entire files. Keep several generations: say, three days' 
    worth. the archived copies can be gzipped.

If you turn the server off overnight, do you maintenance when you reboot. 
    If they're running overnight, make your clients disconnect for a while
    & do the mainteenance then.


Cheers
John Summerfield
Perth, Western Australia
OS2 support, IBM ftp search, LAN configuration info
   @ http://www.iinet.net.au/~summer/