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 OSF1
fd
fd(4) Kernel Interfaces Manual fd(4)NAME
fd - file descriptor files
DESCRIPTION
The /dev/fd file system is a pseudo-file system layered beneath the Virtual File System (VFS). The file descriptor files (fd*) are those
files that are accessible through file descriptors. The file descriptors use the naming convention /dev/fd/0, /dev/fd/1, /dev/fd/2 and so
on up to any number.
To make the /dev/fd file system known to the operating system, you must create the directory with the correct privileges, then you must
mount the file system. The following steps describe how to create the directory, mount the file system both manually and automatically,
and how to dismount the file system: Create the directory using the mkdir and chmod commands: mkdir /dev/fd; chmod 777 /dev/fd Mount the
file system manually using the mount command: mount -t fdfs /dev/fd /dev/fd Mount the file system automatically by editing either the
/etc/fstab file or the /sbin/bcheckrc file.
Add the following entry to the /etc/fstab file: /dev/fd /dev/fd fdfs rw 0 0 This entry mounts the pseudodevice /dev/fd on the
/dev/fd directory with read/write privileges. The file system type is fdfs and the zeros (0) in the remaining fields specify that
the file system is not to be backed up nor can file system checks be performed by the fsck command as this is a virtual file system.
Add the following entry to the /sbin/bcheckrc file: # # mount fdfs # echo 'Mounting /dev/fd filesystem' /sbin/mount -a -v -t fdfs
Again, the /dev/fd file system should not be mounted in this manner if an entire system is to be backed up starting from the root
directory. Dismount the file system using the umount command: umount /dev/fd For correct truncate() behavior on fd files, you must
load your program using the -lsys5 flag.
RESTRICTIONS
The /dev/fd file descriptors should not be exported.
EXAMPLES
The following example show how the open and dup functions have the same effect if file descriptor n is opened:
fd = open("/dev/fd/n", mode);
fd = dup(n);
In the above example, the open function is equal to the creat function and mode is ignored. Using the dup function, subsequent reads or
writes on the fd file descriptor files fail unless the original file descriptor enables the operation.
ERRORS
The following error condition exists: The file descriptor is not valid.
RELATED INFORMATION
Commands: chmod(1), mkdir(1), mount(8).
Functions: creat(2), dup(2), open(2). delim off
fd(4)