During the restore activity this is the cache directory that should be populated:
~/.cache/deja-dup
Instead of
/root/.cache/deja-dup
Does anybody can suggest an idea of why the wrong cache directory is being populated?
I execute deja-dup with a common user i.e. not with root.
Furthermore I tried to confirm the ownership of the "~/.cache/deja-dup" and "~/.cache/duplicity":
Hello,
Here is what I am trying to do.
We have an old Enterprise 250 which we want to phase out. So plan is to move everything running on the 250 to an unused Sun Fire V280R.
Here is what I decided to do:
1. Fresh Solaris 8 install on Sun 280R (disk0). Configure network and install... (1 Reply)
Dear All ;
first how are you every body I'm just subscribed in your forum and i hope i found what i searched for along time .
I'm not a Solaris specialist but i read more to build a Network Management Station depends on Solaris as OS and it is working good now .
my problem is how to perform... (16 Replies)
Hi Buddies,
my pc has two CPU, so CPU1 and CPU2.
I have a perl "a.pl", when i "./a.pl", i can see the CPU1 is full or CPU2 is full, mean only one is full, another one is idle.
Wonderring what shall i do in order to let both CPU to process this a.pl.:(
Thanks (1 Reply)
Hi all,
I have a problem, when I use script with 'expect', accidentally I was deleted root account by "userdel root". Unfortunately, it works, because no other root user login on it. Solaris document said that root cannot delete root, but in my case it works because it deleted by script, not... (7 Replies)
hi guys linux noob here wanting to learn linux scripting, i need help with a backup script that not only allows me to back up my files but restore them to my own personal directory, had a look at some of the coding from the scripts section on this site but still lost.
any help is much appreciated (8 Replies)
Hi men,
I'm testing for my backup&restore job with ZFS.
My server have two disks. I wanna do backup&restore job like ufsdump utility:
Disk0 is rpool(root zpool) and disk1 (backup zpool) will be stored full backup replicates. When rpool zpool have problem, i can "boot cdrom -s" and use my... (5 Replies)
Retro Games has announced that the C64 is back, this time full-sized with a working keyboard for the dedicated retro home-computer fan, available December 2019.
See also:
CNN:
Iconic 80s computer The Commodore 64 to return with fully-functional keyboard
YouTube:
The C64 | Trailer
... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT DEBIAN
dup2
DUP(2) BSD System Calls Manual DUP(2)NAME
dup, dup2 -- duplicate an existing file descriptor
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
dup(int oldd);
int
dup2(int oldd, int newd);
DESCRIPTION
The dup() system call duplicates an existing object descriptor and returns its value to the calling process (newd = dup(oldd)). The argument
oldd is a small non-negative integer index in the per-process descriptor table. The value must be less than the size of the table, which is
returned by getdtablesize(2). The new descriptor returned by the call is the lowest numbered descriptor currently not in use by the process.
The object referenced by the descriptor does not distinguish between oldd and newd in any way. Thus if newd and oldd are duplicate refer-
ences to an open file, read(2), write(2) and lseek(2) calls all move a single pointer into the file, and append mode, non-blocking I/O and
asynchronous I/O options are shared between the references. If a separate pointer into the file is desired, a different object reference to
the file must be obtained by issuing an additional open(2) system call. The close-on-exec flag on the new file descriptor is unset.
In dup2(), the value of the new descriptor newd is specified. If this descriptor is already in use and oldd != newd, the descriptor is first
deallocated as if the close(2) system call had been used. If oldd is not a valid descriptor, then newd is not closed. If oldd == newd and
oldd is a valid descriptor, then dup2() is successful, and does nothing.
RETURN VALUES
The value -1 is returned if an error occurs in either call. The external variable errno indicates the cause of the error.
ERRORS
The dup() and dup2() system calls fail if:
[EBADF] The oldd or newd argument is not a valid active descriptor
[EMFILE] Too many descriptors are active.
SEE ALSO accept(2), close(2), fcntl(2), getdtablesize(2), open(2), pipe(2), socket(2), socketpair(2)STANDARDS
The dup() and dup2() system calls are expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1'').
HISTORY
The dup() and dup2() functions appeared in Version 7 AT&T UNIX.
BSD June 4, 1993 BSD