search for: amandabackup

...ckup user): run amanda every night (check at 2:45 and backup at 3) 45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log * 3 * * * /usr/sbin/amdump /var/log/amanda/crontab/amdump.log The executables are where they are supposed to be and run if you type them in on the command line: [amandabackup at amanda ~]$ ls -l /usr/sbin/amcheck -rwsr-x--- 1 root disk 68624 Dec 29 14:08 /usr/sbin/amcheck [amandabackup at amanda ~]$ ls -l /usr/sbin/amdump -rwxr-xr-x 1 amandabackup disk 9637 Dec 29 14:08 /usr/sbin/amdump Although I'm not sure what the 's' indicates in the permissions of am...

Hi List, Happy New Years and I was hoping to get some help on an ssh issue that I am having. For some reason I am unable to scp to hosts on this network using RSA keys. Here is what I am doing/what is going on; scp the public key to remote host [amandabackup at VIRTCENT18 ~]$ scp ~/.ssh/id_rsa_amdump.pub amandabackup at lb1:~ amandabackup at lb1's password: id_rsa_amdump.pub 100% 408 0.4KB/s 00:00 ssh (w/passwd) to remote host [amandabackup at VIRTCENT18 ~]$ ssh lb1 amandabackup at lb1's password: Last login: Fri...

Hi, I am trying to create a Samba share on /media/winshare with the owner as amandabackup instead of root. But as soon as I mount the Samba share on to the mount point, the permissions for the owner get reverted back to root instead of amandabackup. Attaching a snapshot of how it looks like. http://www.nabble.com/file/p10894282/samba%2Bquery.jpg -- View this message in context: http:...

...t; Processing section "[groups]" Processing section "[winshare]" Loaded services file OK. WARNING: passdb expand explicit = yes is deprecated Server role: ROLE_STANDALONE [global] workgroup = OVE.LOCAL map to guest = Bad User valid users = root, linuxbak, amandabackup force user = amandabackup [homes] comment = Home Directories valid users = %S, %D%w%S read only = No inherit acls = Yes [profiles] comment = Network Profiles Service path = %H read only = No create mask = 0600 directo...

OK, after beating my head against the wall for an hour or so, I finally figured out why I could not ssh from a MacMini (running MacOSX 10.11.6) to my Linux Desktop (running CentOS 6), using the amandabackup account with public key authentification. SELinux! It seems the SELinux won't allow this if the target user's "home" directory is does not have a <mumble>_home_t security context. It there some trick/hack to fix this *specifically* for the amandabackup account? Right...

...ple wrote: > /lib/nut/usbhid-ups -a myups -DD gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission denied lemme see who owns that. huh? amandabackup:nut what the h? Who is supposed to own it and what perms? chown -R nut:nut nut didn't help Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://...

...evel -- -- Unit amanda-udp.service has failed. -- -- The result is failed. Mar 17 08:52:24 sharky4.deepsoft.com systemd[1]: amanda-udp.service failed. sharky4.deepsoft.com% cat /usr/lib/systemd/system/amanda-udp.service [Unit] Description=Amanda Backup System After=local-fs.target [Service] User=amandabackup Group=disk ExecStart=/usr/sbin/amandad -auth=bsd amdump StandardInput=socket What is missing? I have installed (stock CentOS 7 from standard repos): sharky4.deepsoft.com% rpm -qa amanda\* amanda-server-3.3.3-21.el7.x86_64 amanda-client-3.3.3-21.el7.x86_64 amanda-libs-3.3.3-21.el7.x86_64 amanda-...

...s from the backup server to the test backup client. AFAIK everything is setup correctly yet when I ssh as the user to the client I have to type the password. the public key is in the authorized_keys file of the client and permissions all seem correct. Here is a verbose output of the ssh session [amandabackup at VIRTCENT18 .ssh]$ ssh -vvv lb1 OpenSSH_5.6p1lpk, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 debug1: Reading configuration data /etc/ssh/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to lb1 [192.168.1.23] port 22. debug1: Connection established. debug1: identity file /var/lib/amanda/.s...

Okay, this will never come to an end otherwise: I would like to use <http://creativecommons.org/licenses/by-sa/3.0/> as the license for the complete content of the wiki. The content on the wiki is *NOT* licensed at all at the moment. So this call goes out to *ALL* people who have already contributed to the wiki: Is it okay with you to use this license for your content on the wiki? If

...id-ups -a myups -DD > gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: Permission > denied > lemme see who owns that. huh? amandabackup:nut what the h? Who is > supposed to own it and what perms? chown -R nut:nut nut didn't help Needs to be readable by user/group nut, so setting the group as you did, plus "chmod g+r": $ ls -l /etc/nut/ups.conf -rw-r----- 1 root nut 5058 Oct 29 2018 /etc/nut/ups.conf ... altho...

On Sunday 12 May 2019 12:07:13 pm Charles Lepple wrote: > systemctl status nut-driver ● nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-05-10 02:35:09 EDT; 2 days ago Ok, I'll byte, the only usnhid-ups on the system is on

...Server=[Samba 3.0.22-13.30-1290-SUSE-SLES10] Server Comment --------- ------- Workgroup Master --------- ------- OVE-VICKI OVE-DC01 OVE.COM DEVDB001 OVE.LOCAL AMANDABACKUP Can someone tell me what I am doing wrong? Thanks. -- View this message in context: http://www.nabble.com/%22Access-denied%22-error-on-Samba-mount-tf4629545.html#a13219213 Sent from the Samba - General mailing list archive at Nabble.com.

...off # description:? The client for the Amanda backup system.\ #?????????????? This must be on for systems being backed up\ #?????????????? by Amanda. service amanda { ??? disable???????? = no ??? socket_type???? = dgram ??? protocol??? ??? = udp ??? wait??? ??? ??? = yes ??? user??? ??? ??? = amandabackup ??? group??? ??? ?? = disk ??? server??? ??? ? = /usr/sbin/amandad # Configure server_args for the authentication type you will be using, # and the services you wish to allow the amanda server and/or recovery # clients to use. # # Change the -auth= entry to reflect the authentication type you use...

...gene at coyote:~$ /lib/nut/usbhid-ups -a myups -DD > > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > > USB communication driver 0.33 > > Can't open /etc/nut/ups.conf: Can't open /etc/nut/ups.conf: > > Permission denied > > lemme see who owns that. huh? amandabackup:nut what the h? Who is > > supposed to own it and what perms? chown -R nut:nut nut didn't help > > Needs to be readable by user/group nut, so setting the group as you > did, plus "chmod g+r": > That seemed to work, making > $ ls -l /etc/nut/ups.conf > -rw-r--...