search for: saveconfigs

Hi, I am working to get iscsi running using targetcli. So far everything seems to be working except for the fact that when I run saveconfig, exit the targetcli shell and reboot, the iscsi configs are gone. If I run restoreconfig, the configuration gets reloaded and all is well. Can someone tell me how to get the targetcli configuration to persist through a reboot? Regards, -- Tom me at

...(such as something similar to cfengine''s HashCommentLinesContaining), users could start using them, and Luke could mark whether the function will become native to Puppet after the API settles down. For example, I have defined backup-dir so that all I have to do is this: backup-dir { "SaveConfigs": path => "/", directory => "etc", destination => "main", compression => 2; }

Hi, I had previously posted about connecting an AS5300 to * via SIP/H323. I got it to work via SIP, but only 1 call at a time would work, and if a user from the * side hung up, the cisco would'nt catch the hangup. I an now trying to hook up to the cisco via E1, with a Sangoma A101 card in my * box. I would like it such that I call from * via E1/PRI to the cisco, and call out via R2 to

Hi all, I have some problems with my gvinum setup after the system panic'ed. Afterwards the system fails finding the plexes to the subdisks (or at least that is what I can understand after having searched the gvinum source code for the error string in the DMESG log..) The machine is an IBM Netfinity 5000 and the internal HW self tests does not find any errors in the hw. Luckily my root is

Hi, Michael I have met ext4 error when using vhost_scsi on arm64 platform, and suspect it is vhost_scsi issue. Ext4 error when testing virtio_scsi & vhost_scsi No issue: 1. virtio_scsi, ext4 2. vhost_scsi & virtio_scsi, ext2 3. Instead of vhost, also tried loopback and no problem. Using loopback, host can use the new block device, while vhost is used by guest (qemu).

Hi, Michael I have met ext4 error when using vhost_scsi on arm64 platform, and suspect it is vhost_scsi issue. Ext4 error when testing virtio_scsi & vhost_scsi No issue: 1. virtio_scsi, ext4 2. vhost_scsi & virtio_scsi, ext2 3. Instead of vhost, also tried loopback and no problem. Using loopback, host can use the new block device, while vhost is used by guest (qemu).