On Mon, 28 Mar 2016 10:19:12 +0200, Paul Kelly wrote:
> On 03/28/16 04:05, Todd C. Miller wrote:
> > I think it's best to just check the parent directories first and
> > then create the temp name.
> >
> > - todd
>
> This works for me and avoids my hacking around with new. I added a few
> e
On 03/28/16 04:05, Todd C. Miller wrote:
> I think it's best to just check the parent directories first and
> then create the temp name.
>
> - todd
This works for me and avoids my hacking around with new. I added a few
extra destination directories and it seems to hold up OK. Thanks!
paul@ti
I had a request for more information about how to replicate this. Here's
a stripped back example that demonstrates the problem.
paul@tiger:~/workspace/push/cm: cat ./distfile
./hosts/aspireone/etc/doas.conf -> ${HOST}
install staging/etc ;
paul@tiger:~/workspace/push/cm: cat ./hosts/as
I think it's best to just check the parent directories first and
then create the temp name.
- todd
Index: server.c
===
RCS file: /cvs/src/usr.bin/rdistd/server.c,v
retrieving revision 1.40
diff -u -p -u -r1.40 server.c
--- server.c
Dear misc,
I am playing with rdist for some basic management of config files on
remote machines. I have run into an issue with rdistd where it
(apparently) has to create two or more directories in succession and
then copy files across to those newly created directories.
aspireone: updating
5 matches
Mail list logo
